[YARN-2013] The diagnostics is always the ExitCodeException stack when the container crashes

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.6.0
• Component/s: nodemanager
• Assignee: Tsuyoshi Ozawa
• Reporter: Zhijie Shen
• Created: 01/May/14 06:22
• Updated: 25/Oct/19 20:27
• Resolved: 22/Jul/14 03:05

Description

When a container crashes, ExitCodeException will be thrown from Shell. Default/LinuxContainerExecutor captures the exception, put the exception stack into the diagnostic. Therefore, the exception stack is always the same.

        String diagnostics = "Exception from container-launch: \n"
            + StringUtils.stringifyException(e) + "\n" + shExec.getOutput();
        container.handle(new ContainerDiagnosticsUpdateEvent(containerId,
            diagnostics));

In addition, it seems that the exception always has a empty message as there's no message from stderr. Hence the diagnostics is not of much use for users to analyze the reason of container crash.

Issue Links

• is related to: YARN-2242 Improve exception information on AM launch crashes