You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-dev@hadoop.apache.org by "Mohammad Kamrul Islam (JIRA)" <ji...@apache.org> on 2013/12/23 04:16:50 UTC

[jira] [Created] (MAPREDUCE-5694) MR AM container syslog is empty

Mohammad Kamrul Islam created MAPREDUCE-5694:
------------------------------------------------

             Summary: 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


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)