[CHUKWA-28] Add late initialization to the chukwa log4j appender

• Type: Improvement
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Assignee: Jerome Boulon
• Reporter: Jerome Boulon
• Created: 15/Jan/09 19:12
• Updated: 27/Mar/09 22:40
• Resolved: 27/Mar/09 22:40

Description

With the current Chukwa log4j implementation, if you define a static log4j configuration the appender is initialized at creation time.

This may cause some problems for example with Hadoop Audit log or Metrics context, if the log4j properties are statically defined then a userX running an hadoop command will trigger a permission denied exception since the appender will try to initialize itself and therefore try to create a file under userX ownership for each appender even if not data is going to be written to it.

The goal is to delay this initialization until the first message is actually written to that log so this kind of issue could easily be avoided.

Issue Links

• is blocked by: HADOOP-5042 Add expiration handling to the chukwa log4j appender