[AMBARI-25565] ConfigHelper.java logging consumes most server logs for clusters with many hosts

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.7.5
• Fix Version/s: 2.8.0, 2.7.6
• Component/s: ambari-server
• Assignee: Dmitry Lysnichenko
• Reporter: Dmytro Vitiuk
• Created: 07/Oct/20 14:22
• Updated: 22/Nov/22 08:47
• Resolved: 07/Oct/20 15:26

Description

Now for each config update we calculate config changes for each host in the cluster. There we are logging all config versions that are used for config changes calculation:

2020-10-03 20:12:46,872  INFO [pool-28-thread-1] ConfigHelper:2051 - For configs update on host 3 will be used following cluster desired configs {zoo.cfg={tag=TOPOLOGY_RESOLVED}, zookeeper-log4j={tag=TOPOLOGY_RESOLVED...

So in the case we have a lot of hosts in the cluster most server log capacity is spent on config versions logging. We need to reduce logging level for some log calls in ConfigHelper.getHostActualConfigsExcludeCluster(...).

Issue Links

• links to: GitHub PR#3550
• links to: pull request