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 "Patrick Hunt (Created) (JIRA)" <ji...@apache.org> on 2012/03/07 20:52:57 UTC

[jira] [Created] (HADOOP-8149) cap space usage of default log4j rolling policy

cap space usage of default log4j rolling policy 
------------------------------------------------

                 Key: HADOOP-8149
                 URL: https://issues.apache.org/jira/browse/HADOOP-8149
             Project: Hadoop Common
          Issue Type: Improvement
          Components: conf
            Reporter: Patrick Hunt


I've seen several critical production issues because logs are not automatically removed after some time and accumulate. Changes to Hadoop's default log4j file appender would help with this.

I recommend we move to an appender which:

1) caps the max file size (configurable)
2) caps the max number of files to keep (configurable)
3) uses rolling file appender rather than DRFA, see the warning here:
http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/DailyRollingFileAppender.html
Specifically: "DailyRollingFileAppender has been observed to exhibit synchronization issues and data loss."

We'd lose (based on the default log4j configuration) the daily rolling aspect, however increase reliability.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira