You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Ramya Sunil (Created) (JIRA)" <ji...@apache.org> on 2011/10/25 23:08:32 UTC
[jira] [Created] (MAPREDUCE-3269) Jobsummary logs not being moved
to a separate file
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
Priority: Blocker
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
[jira] [Updated] (MAPREDUCE-3269) Jobsummary logs not being moved
to a separate file
Posted by "Mahadev konar (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mahadev konar updated MAPREDUCE-3269:
-------------------------------------
Attachment: MAPREDUCE-3269.patch
Minor fixes to set default to INFO, JSA in yarn-daemon.sh. Doing some testing.
> 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
> Priority: Blocker
> Attachments: 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
[jira] [Assigned] (MAPREDUCE-3269) Jobsummary logs not being moved
to a separate file
Posted by "Mahadev konar (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mahadev konar reassigned MAPREDUCE-3269:
----------------------------------------
Assignee: Mahadev konar
> 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
> Attachments: 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
[jira] [Commented] (MAPREDUCE-3269) Jobsummary logs not being moved
to a separate file
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13135958#comment-13135958 ]
Hudson commented on MAPREDUCE-3269:
-----------------------------------
Integrated in Hadoop-Hdfs-0.23-Build #51 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/51/])
Merge -c 1188999 from trunk to branch-0.23 to complete fix for MAPREDUCE-3269.
acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1189000
Files :
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/bin/yarn
* /hadoop/common/branches/branch-0.23/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
[jira] [Commented] (MAPREDUCE-3269) Jobsummary logs not being moved
to a separate file
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13135669#comment-13135669 ]
Hudson commented on MAPREDUCE-3269:
-----------------------------------
Integrated in Hadoop-Mapreduce-0.23-Commit #50 (See [https://builds.apache.org/job/Hadoop-Mapreduce-0.23-Commit/50/])
Merge -c 1188999 from trunk to branch-0.23 to complete fix for MAPREDUCE-3269.
acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1189000
Files :
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/bin/yarn
* /hadoop/common/branches/branch-0.23/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
[jira] [Commented] (MAPREDUCE-3269) Jobsummary logs not being moved
to a separate file
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13135651#comment-13135651 ]
Hudson commented on MAPREDUCE-3269:
-----------------------------------
Integrated in Hadoop-Common-0.23-Commit #50 (See [https://builds.apache.org/job/Hadoop-Common-0.23-Commit/50/])
Merge -c 1188999 from trunk to branch-0.23 to complete fix for MAPREDUCE-3269.
acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1189000
Files :
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/bin/yarn
* /hadoop/common/branches/branch-0.23/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
[jira] [Commented] (MAPREDUCE-3269) Jobsummary logs not being moved
to a separate file
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13135666#comment-13135666 ]
Hudson commented on MAPREDUCE-3269:
-----------------------------------
Integrated in Hadoop-Mapreduce-trunk-Commit #1167 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/1167/])
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
[jira] [Commented] (MAPREDUCE-3269) Jobsummary logs not being moved
to a separate file
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13135939#comment-13135939 ]
Hudson commented on MAPREDUCE-3269:
-----------------------------------
Integrated in Hadoop-Mapreduce-trunk #872 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/872/])
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
[jira] [Updated] (MAPREDUCE-3269) Jobsummary logs not being moved
to a separate file
Posted by "Arun C Murthy (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arun C Murthy updated MAPREDUCE-3269:
-------------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
I just committed this. Thanks Mahadev!
> 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
[jira] [Commented] (MAPREDUCE-3269) Jobsummary logs not being moved
to a separate file
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13135646#comment-13135646 ]
Hudson commented on MAPREDUCE-3269:
-----------------------------------
Integrated in Hadoop-Hdfs-trunk-Commit #1231 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/1231/])
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
[jira] [Commented] (MAPREDUCE-3269) Jobsummary logs not being moved
to a separate file
Posted by "Hadoop QA (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13135575#comment-13135575 ]
Hadoop QA commented on MAPREDUCE-3269:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12500777/MAPREDUCE-3269.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
-1 javadoc. The javadoc tool appears to have generated 8 warning messages.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
-1 findbugs. The patch appears to introduce 165 new Findbugs (version 1.3.9) warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
+1 core tests. The patch passed unit tests in .
+1 contrib tests. The patch passed contrib unit tests.
Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1142//testReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1142//artifact/trunk/hadoop-mapreduce-project/patchprocess/newPatchFindbugsWarningshadoop-mapreduce-client-common.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1142//artifact/trunk/hadoop-mapreduce-project/patchprocess/newPatchFindbugsWarningshadoop-mapreduce-client-app.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1142//artifact/trunk/hadoop-mapreduce-project/patchprocess/newPatchFindbugsWarningshadoop-mapreduce-client-core.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1142//artifact/trunk/hadoop-mapreduce-project/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-resourcemanager.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1142//artifact/trunk/hadoop-mapreduce-project/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-nodemanager.html
Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1142//console
This message is automatically generated.
> 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
[jira] [Commented] (MAPREDUCE-3269) Jobsummary logs not being moved
to a separate file
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13135641#comment-13135641 ]
Hudson commented on MAPREDUCE-3269:
-----------------------------------
Integrated in Hadoop-Hdfs-0.23-Commit #51 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Commit/51/])
Merge -c 1188999 from trunk to branch-0.23 to complete fix for MAPREDUCE-3269.
acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1189000
Files :
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/bin/yarn
* /hadoop/common/branches/branch-0.23/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
[jira] [Updated] (MAPREDUCE-3269) Jobsummary logs not being moved
to a separate file
Posted by "Mahadev konar (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mahadev konar updated MAPREDUCE-3269:
-------------------------------------
Attachment: MAPREDUCE-3269.patch
Tested the fix. This works.
> 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
[jira] [Commented] (MAPREDUCE-3269) Jobsummary logs not being moved
to a separate file
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13135643#comment-13135643 ]
Hudson commented on MAPREDUCE-3269:
-----------------------------------
Integrated in Hadoop-Common-trunk-Commit #1153 (See [https://builds.apache.org/job/Hadoop-Common-trunk-Commit/1153/])
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
[jira] [Commented] (MAPREDUCE-3269) Jobsummary logs not being moved
to a separate file
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13135947#comment-13135947 ]
Hudson commented on MAPREDUCE-3269:
-----------------------------------
Integrated in Hadoop-Mapreduce-0.23-Build #63 (See [https://builds.apache.org/job/Hadoop-Mapreduce-0.23-Build/63/])
Merge -c 1188999 from trunk to branch-0.23 to complete fix for MAPREDUCE-3269.
acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1189000
Files :
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/bin/yarn
* /hadoop/common/branches/branch-0.23/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
[jira] [Updated] (MAPREDUCE-3269) Jobsummary logs not being moved
to a separate file
Posted by "Mahadev konar (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mahadev konar updated MAPREDUCE-3269:
-------------------------------------
Fix Version/s: 0.23.0
Status: Patch Available (was: Open)
> 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
[jira] [Commented] (MAPREDUCE-3269) Jobsummary logs not being moved
to a separate file
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ 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