You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Jerome Boulon (JIRA)" <ji...@apache.org> on 2009/03/04 00:26:56 UTC

[jira] Updated: (HADOOP-5058) Add late initialization to the chukwa log4j appender

     [ https://issues.apache.org/jira/browse/HADOOP-5058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jerome Boulon updated HADOOP-5058:
----------------------------------

    Attachment: HADOOP-5058-2.patch

copy late-log4j.properties to the right location

>  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.