[jira] Commented: (ZOOKEEPER-223) default log4j root logger configuration has neg perf impact with no benefit, change default level to INFO

["Mahadev konar (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648181#action_12648181 ] 

Mahadev konar commented on ZOOKEEPER-223:
-----------------------------------------

+1 for the patch... 

> default log4j root logger configuration has neg perf impact with no benefit, change default level to INFO
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-223
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-223
>             Project: Zookeeper
>          Issue Type: Improvement
>          Components: java client, server
>    Affects Versions: 3.0.0
>            Reporter: Patrick Hunt
>            Assignee: Patrick Hunt
>             Fix For: 3.0.1, 3.1.0
>
>         Attachments: ZOOKEEPER-223.patch
>
>
> The default log4j.properties has:
> log4j.rootLogger=DEBUG, CONSOLE
> where the console appender is only outputting INFO level and above.
> This is resulting in a large number of debug logs being generated, which are all filtered out by the console appender (by default there are no other appenders used)
> We need to change the default rootLogger to INFO level, which will resolve this issue.
> Users are free to change this of course -- most likely they would only do this when debugging an issue, and would not want to run in DEBUG in production (again, they are free to choose).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.