[MAPREDUCE-5694] MR AM container syslog is empty

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.2.0
• Fix Version/s: 2.3.0
• Hadoop Flags: Reviewed
• Assignee: Mohammad Islam
• Reporter: Mohammad Islam
• Created: 23/Dec/13 03:15
• Updated: 24/Feb/14 20:58
• Resolved: 28/Dec/13 17:52

Description

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.

Issue Links

• breaks: MAPREDUCE-5730 AM log is truncated