[YARN-564] Job history logs do not log anything when JVM fails to start

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Duplicate
• Affects Version/s: 3.0.0-alpha1
• Labels: usability

Environment

Ubuntu 64bit

• Assignee: Jian He
• Reporter: Gopal Vijayaraghavan
• Created: 11/Apr/13 09:48
• Updated: 12/May/16 18:29
• Resolved: 18/Dec/13 05:25

Description

If the -Xmx line in a java invocation has errors such as is possible with quoting issues as would be possible with hive

hive> set mapred.map.child.java.opts="-server -Xmx2248m -Djava.net.preferIPv4Stack=true";

The diagnostic error message says

FAILED: Execution Error, return code 2 from org.apache.hadoop.hive.ql.exec.MapRedTask

The job history UI is rather unhelpful and the UI says

Attmpt state missing from History : marked as KILLED

And the log files are not available and instead show

Logs not available for attempt_1365673149565_0002_m_000000_3. Aggregation may not be complete, Check back later or try the nodemanager at :-1

Issue Links

• is related to: YARN-522 [Umbrella] Better reporting for crashed/Killed AMs and Containers
• relates to: YARN-814 Difficult to diagnose a failed container launch when error due to invalid environment variable