[
https://issues.apache.org/jira/browse/MAPREDUCE-5694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13855914#comment-13855914
]
Hadoop QA commented on MAPREDUCE-5694:
--------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12620250/MAPREDUCE-5694.1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. 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.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4280//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4280//console
This message is automatically generated.
> MR AM container syslog is empty
> ---------------------------------
>
> Key: MAPREDUCE-5694
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5694
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 2.2.0
> Reporter: Mohammad Kamrul Islam
> Assignee: Mohammad Kamrul Islam
> Attachments: MAPREDUCE-5694.1.patch
>
>
> When the property "mapreduce.task.userlog.limit.kb" is set non-zero in
> mapped-site.xml, AM container syslog remains empty. Without the log, it is
> hard to identify the cause of any MR AM failure.
> However, if "mapreduce.task.userlog.limit.kb" is not set (or defaulted to
> 0), syslog contents are correct.
>
> Bug details:
> For non zero "mapreduce.task.userlog.limit.kb", the code caches the log
> contents into memory, waited to be written to file when close() method is
> called at the end(Ref: ContainerLogAppender.java).
> Explicit call of LogManager.shutdown() from the main()
> (REF:MRAppMaster.java), ultimately call the *Appender.close().
> Root Cause:
> LogManager.shutdown() is not being called from MRAppMaster.java.
> Similar steps were taken correctly in YarnChild.java.
>
>
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
