Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-dev@hadoop.apache.org
Date: Fri, 23 Sep 2011 18:51:26 +0000 (UTC)
From: "Ramya Sunil (JIRA)" <jira@apache.org>
To: common-dev@hadoop.apache.org
Message-ID: 
 <124688673.7659.1316803886263.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (HADOOP-7679) log4j.properties templates does not
 define mapred.jobsummary.logger
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

log4j.properties templates does not define mapred.jobsummary.logger
-------------------------------------------------------------------

                 Key: HADOOP-7679
                 URL: https://issues.apache.org/jira/browse/HADOOP-7679
             Project: Hadoop Common
          Issue Type: Bug
          Components: conf
    Affects Versions: 0.20.205.0
            Reporter: Ramya Sunil
            Assignee: Ramya Sunil
             Fix For: 0.20.205.0


In templates/conf/hadoop-env.sh, HADOOP_JOBTRACKER_OPTS is defined as -Dsecurity.audit.logger=INFO,DRFAS -Dmapred.audit.logger=INFO,MRAUDIT -Dmapred.jobsummary.logger=INFO,JSA ${HADOOP_JOBTRACKER_OPTS}
However, in templates/conf/hadoop-env.sh, instead of mapred.jobsummary.logger, hadoop.mapreduce.jobsummary.logger is defined as follows:
hadoop.mapreduce.jobsummary.logger=${hadoop.root.logger}
This is preventing collection of jobsummary logs.

We have to consistently use mapred.jobsummary.logger in the templates.


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