hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Hunt (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-8149) cap space usage of default log4j rolling policy
Date Wed, 28 Mar 2012 22:03:29 GMT

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

Patrick Hunt updated HADOOP-8149:

    Attachment: HADOOP-8149.patch

I believe this updated patch addresses everyone's concerns:

1) upped the cap to 5gb (256M * 20)
2) addressed the security logger concerns for nn/2nn OPTS
3) I left DN as is for the time being per Kihwal's comment (indeed the SecurityLogger seems
4) HADOOP_ROOT_LOGGER is handled in hadoop-config.sh and not overridden by the nn/2nn OPTS,
so I believe we're good with that as well.
> 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
>            Assignee: Patrick Hunt
>         Attachments: HADOOP-8149.patch, HADOOP-8149.patch, HADOOP-8149.patch, HADOOP-8149.patch
> 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


View raw message