[ https://issues.apache.org/jira/browse/HADOOP-7679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114464#comment-13114464
]
Matt Foley commented on HADOOP-7679:
------------------------------------
+1 code review.
Committed to 0.20-security and 0.20.205.
Thanks, Ramya!
> 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
>
> Attachments: HADOOP-7679.txt, HADOOP-7679v2.txt
>
>
> 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
|