[jira] [Commented] (HADOOP-14515) Specifically configure zookeeper-related log levels in KMS log4j

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (HADOOP-14515) Specifically configure zookeeper-related log levels in KMS log4j

JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/HADOOP-14515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16054564#comment-16054564 ]

Yongjun Zhang commented on HADOOP-14515:
----------------------------------------

Thanks [~xiaochen], +1 on the 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
>         Attachments: HADOOP-14515.01.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: [hidden email]
For additional commands, e-mail: [hidden email]