Mailing-List: contact mapreduce-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-dev@hadoop.apache.org
Date: Wed, 9 Mar 2011 20:06:00 +0000 (UTC)
From: "Todd Lipcon (JIRA)" <jira@apache.org>
To: mapreduce-dev@hadoop.apache.org
Message-ID: 
 <2005426554.8963.1299701160616.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Created: (MAPREDUCE-2372) TaskLogAppender mechanism
 shouldn't be set in log4j.properties
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

TaskLogAppender mechanism shouldn't be set in log4j.properties
--------------------------------------------------------------

                 Key: MAPREDUCE-2372
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2372
             Project: Hadoop Map/Reduce
          Issue Type: Improvement
          Components: task
    Affects Versions: 0.22.0
            Reporter: Todd Lipcon
             Fix For: 0.22.0


The TaskLogAppender log4j appender relies on using log4j.properties to pass in some Java system properties into properties of the logger. This is problematic since we've often found that users have customized log4j.properties and don't upgrade it when they upgrade the version of Hadoop.

Since this is really an internal mechanism of how the task runner passes task info to the TLA, we shouldn't rely on these settings in log4j.properties at all. Rather, we should just get the system properties directly from System.getProperty.

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