You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Xiao Chen (JIRA)" <ji...@apache.org> on 2017/06/28 04:02:00 UTC
[jira] [Reopened] (HADOOP-14515) Specifically configure
zookeeper-related log levels in KMS log4j
[ https://issues.apache.org/jira/browse/HADOOP-14515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xiao Chen reopened HADOOP-14515:
--------------------------------
It seems I missed the main log4j here.... attaching addendum patch.
> Specifically configure zookeeper-related log levels in KMS log4j
> ----------------------------------------------------------------
>
> Key: HADOOP-14515
> URL: https://issues.apache.org/jira/browse/HADOOP-14515
> Project: Hadoop Common
> Issue Type: Improvement
> Components: kms
> Affects Versions: 2.6.0
> Reporter: Xiao Chen
> Assignee: Xiao Chen
> Fix For: 2.9.0, 3.0.0-alpha4, 2.8.2
>
> Attachments: HADOOP-14515.01.patch, HADOOP-14515.addendum.patch
>
>
> When investigating a case, we tried to turn on KMS DEBUG by setting the root logger in the log4j to DEBUG. This ends up making {{org.apache.zookeeper.ClientCnxn}} to generate 199.2M out of a 200M log file, which made the kms.log rotate very quickly.
> We should keep zookeeper's log unaffected by the root logger, and only turn it on when interested.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org