Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <1261593506.1236037796167.JavaMail.jira@brutus>
Date: Mon, 2 Mar 2009 15:49:56 -0800 (PST)
From: "Ari Rabkin (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-5058)  Add late initialization to the
 chukwa log4j appender
In-Reply-To: <1697914188.1232046779570.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-5058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678163#action_12678163 ] 

Ari Rabkin commented on HADOOP-5058:
------------------------------------

I don't understand why we need the chmod -- what are the files created as, by default?  

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