[jira] [Commented] (YARN-2013) The diagnostics is always the ExitCodeException stack when the container crashes

["Tsuyoshi OZAWA (JIRA)" <ji...@apache.org>]

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

Tsuyoshi OZAWA commented on YARN-2013:
--------------------------------------

+1(non-binding), in fact I often faces the problem in Tez project. This behavior make it difficult to debug YARN Apps.

TestContainerLaunch#testContainerLaunchStdoutAndStderrDiagnostics() confirms that Exception.getMessages() returns the stderr's message. We should include the message into the diagnostics.

> The diagnostics is always the ExitCodeException stack when the container crashes
> --------------------------------------------------------------------------------
>
>                 Key: YARN-2013
>                 URL: https://issues.apache.org/jira/browse/YARN-2013
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: nodemanager
>            Reporter: Zhijie Shen
>
> 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. 
> {code}
>         String diagnostics = "Exception from container-launch: \n"
>             + StringUtils.stringifyException(e) + "\n" + shExec.getOutput();
>         container.handle(new ContainerDiagnosticsUpdateEvent(containerId,
>             diagnostics));
> {code}
> 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.



--
This message was sent by Atlassian JIRA
(v6.2#6252)