Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Wed, 26 Oct 2011 13:01:35 +0000 (UTC)
From: "Hudson (Commented) (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <1138696671.17872.1319634095830.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <976168753.15173.1319576912280.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (MAPREDUCE-3269) Jobsummary logs not being moved
 to a separate file
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hudson commented on MAPREDUCE-3269:
-----------------------------------

Integrated in Hadoop-Hdfs-trunk #844 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/844/])
    MAPREDUCE-3269. Fixed log4j properties to correctly set logging options for JobHistoryServer vis-a-vis JobSummary logs. Contributed by Mahadev Konar.

acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1188999
Files : 
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/bin/yarn
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/bin/yarn-daemon.sh

                
> Jobsummary logs not being moved to a separate file
> --------------------------------------------------
>
>                 Key: MAPREDUCE-3269
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3269
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.0
>            Reporter: Ramya Sunil
>            Assignee: Mahadev konar
>            Priority: Blocker
>             Fix For: 0.23.0
>
>         Attachments: MAPREDUCE-3269.patch, MAPREDUCE-3269.patch
>
>
> The jobsummary logs are not being moved to a separate file. Below is the configuration in log4j.properties:
> {noformat}
> mapred.jobsummary.logger=INFO,console
> log4j.logger.org.apache.hadoop.mapreduce.jobhistory.JobSummary=${mapred.jobsummary.logger}
> log4j.additivity.org.apache.hadoop.mapreduce.jobhistory.JobSummary=false
> log4j.appender.JSA=org.apache.log4j.DailyRollingFileAppender
> log4j.appender.JSA.File=${hadoop.log.dir}/mapred-jobsummary.log
> log4j.appender.JSA.layout=org.apache.log4j.PatternLayout
> log4j.appender.JSA.layout.ConversionPattern=%d{ISO8601} %p %c{2}: %m%n
> log4j.appender.JSA.DatePattern=.yyyy-MM-dd
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira