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

["Dmitry Lysnichenko (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMBARI-25565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dmitry Lysnichenko resolved AMBARI-25565.
-----------------------------------------
    Resolution: Fixed

> ConfigHelper.java logging consumes most server logs for clusters with many hosts
> --------------------------------------------------------------------------------
>
>                 Key: AMBARI-25565
>                 URL: https://issues.apache.org/jira/browse/AMBARI-25565
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.7.5
>            Reporter: Dmytro Vitiuk
>            Assignee: Dmitry Lysnichenko
>            Priority: Major
>             Fix For: 2.7.6
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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:
> {code}
> 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...
> {code}
> 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(...).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)