hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xiao Chen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-14515) Specifically configure zookeeper-related log levels in KMS log4j
Date Wed, 28 Jun 2017 06:50:00 GMT

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

Xiao Chen updated HADOOP-14515:
-------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Committed the addendum patch to trunk, branch-2 and branch-2.8.
Thanks.

> 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-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org


Mime
View raw message