hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-4757) Replace log4j.properties with log4j.xml
Date Sat, 02 Jul 2011 09:43:28 GMT

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

Steve Loughran commented on HADOOP-4757:
----------------------------------------

There's still a log4j.properties in hadoop-common 0.20.203, which causes problems for any
app downstream that uses the JAR, even if it doesn't show up in a hadoop.sh driven run


Some options
# Remove all log4j config files in the JAR
# move to the XML format and store it in a different name in the JAR, so you can switch to
it via a JVM properties
I'll go for number two

> Replace log4j.properties with log4j.xml
> ---------------------------------------
>
>                 Key: HADOOP-4757
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4757
>             Project: Hadoop Common
>          Issue Type: Improvement
>    Affects Versions: 0.20.203.0
>            Reporter: Alex Loddengaard
>            Assignee: Alex Loddengaard
>            Priority: Minor
>         Attachments: log4j_xml_config.patch, log4j_xml_config_v2.patch
>
>
> Certain log4j features are not configurable via the log4j.properties file, not to mention
the log4j.properties file is messy.  For this reason, we should transition to a XML file to
configure log4j.  The .properties vs. .xml argument has only come up in HADOOP-211, where
the XML configuration was vetoed for Tomcat integration issues.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message