You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@chukwa.apache.org by "Ari Rabkin (JIRA)" <ji...@apache.org> on 2009/03/24 23:27:53 UTC
[jira] Commented: (CHUKWA-28) Add late initialization to the
chukwa log4j appender
[ https://issues.apache.org/jira/browse/CHUKWA-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688913#action_12688913 ]
Ari Rabkin commented on CHUKWA-28:
----------------------------------
I'd like to commit this, but the patch has gone stale. :( Jerome, can you regenerate?
> Add late initialization to the chukwa log4j appender
> -----------------------------------------------------
>
> Key: CHUKWA-28
> URL: https://issues.apache.org/jira/browse/CHUKWA-28
> Project: Hadoop Chukwa
> Issue Type: Improvement
> 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.