hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-5694) MR AM container syslog is empty
Date Sat, 28 Dec 2013 21:48:50 GMT

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

Hudson commented on MAPREDUCE-5694:
-----------------------------------

SUCCESS: Integrated in Hadoop-trunk-Commit #4932 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/4932/])
MAPREDUCE-5694. Fixed MR AppMaster to shutdown the LogManager so as to avoid losing syslog
in some conditions. Contributed by Mohammad Kamrul Islam. (vinodkv: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1553879)
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/MRAppMaster.java


> 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
>             Fix For: 2.4.0
>
>         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)

Mime
View raw message