[ZOOKEEPER-1435] cap space usage of default log4j rolling policy

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.4.3, 3.3.5, 3.5.0
• Fix Version/s: 3.5.0
• Component/s: scripts
• Hadoop Flags: Reviewed
• Assignee: Patrick D. Hunt
• Reporter: Patrick D. Hunt
• Created: 28/Mar/12 16:33
• Updated: 30/Mar/12 01:08
• Resolved: 30/Mar/12 01:08

Description

Our current log4j log rolling policy (for ROLLINGFILE) doesn't cap the max logging space used. This can be a problem in production systems. See similar improvements recently made in hadoop: HADOOP-8149

For ROLLINGFILE only, I believe we should change the default threshold to INFO and cap the max space to something reasonable, say 5g (max file size of 256mb, max file count of 20). These will be the defaults in log4j.properties, which you would also be able to override from the command line.

Issue Links

• is related to: HADOOP-8149 cap space usage of default log4j rolling policy