[
https://issues.apache.org/jira/browse/HADOOP-5058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677895#action_12677895
]
Hadoop QA commented on HADOOP-5058:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12401153/HADOOP-5058.patch
against trunk revision 748861.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 4 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 Eclipse classpath. The patch retains Eclipse classpath integrity.
-1 release audit. The applied patch generated 799 release audit warnings
(more than the trunk's current 798 warnings).
-1 core tests. The patch failed core unit tests.
-1 contrib tests. The patch failed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/29/testReport/
Release audit warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/29/artifact/trunk/current/releaseAuditDiffWarnings.txt
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/29/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/29/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/29/console
This message is automatically generated.
> 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.
