[ https://issues.apache.org/jira/browse/HADOOP-5058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678170#action_12678170
]
Jerome Boulon commented on HADOOP-5058:
---------------------------------------
It depends on the user umask and since chukwaAgent is not running as a privilege user, most
of the time you'll not have access to it.
BTW, this has been there for a while in Log4JMetricsContext.java
> 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.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.
|