[
https://issues.apache.org/jira/browse/HADOOP-5058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Yang updated HADOOP-5058:
------------------------------
Release Note:
What is new in HADOOP-5058:
Added late initialization for Chukwa Log4j appender for Hadoop metrics and
audit log appender.
was:
A junit is included but if you want to see the default behavior:
Edit:
src/contrib/chukwa/src/test/org/apache/hadoop/chukwa/inputtools/log4j/late-log4j.properties
and change it according to:
log4j.appender.R=org.apache.log4j.RollingFileAppender
#log4j.appender.R=org.apache.hadoop.chukwa.inputtools.log4j.ChukwaDailyRollingFileAppender
Status: Patch Available (was: Open)
Comment from previous release note:
A junit is included but if you want to see the default behavior:
Edit:
src/contrib/chukwa/src/test/org/apache/hadoop/chukwa/inputtools/log4j/late-log4j.properties
and change it according to:
log4j.appender.R=org.apache.log4j.RollingFileAppender
#log4j.appender.R=org.apache.hadoop.chukwa.inputtools.log4j.ChukwaDailyRollingFileAppender
> Add late initialization to the chukwa log4j appender
> -----------------------------------------------------
>
> Key: HADOOP-5058
> URL: https://issues.apache.org/jira/browse/HADOOP-5058
> Project: Hadoop Core
> Issue Type: Improvement
> Components: contrib/chukwa
> Reporter: Jerome Boulon
> Assignee: Jerome Boulon
> Attachments: HADOOP-5058-2.patch, HADOOP-5058.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
