[
https://issues.apache.org/jira/browse/HADOOP-14515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16066031#comment-16066031
]
Hudson commented on HADOOP-14515:
---------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #11939 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/11939/])
HADOOP-14515. Addendum. Specifically configure zookeeper-related log (xiao: rev
fb5ee3fafbe5a7390aa706cdeef12732051b58ee)
* (edit) hadoop-common-project/hadoop-kms/src/main/conf/kms-log4j.properties
> 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: [email protected]
For additional commands, e-mail: [email protected]
