[
https://issues.apache.org/jira/browse/YARN-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14070352#comment-14070352
]
Hudson commented on YARN-2013:
------------------------------
SUCCESS: Integrated in Hadoop-Mapreduce-trunk #1839 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1839/])
YARN-2013. The diagnostics is always the ExitCodeException stack when the
container crashes. (Contributed by Tsuyoshi OZAWA) (junping_du:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1612449)
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/DefaultContainerExecutor.java
*
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/LinuxContainerExecutor.java
*
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/TestDefaultContainerExecutor.java
*
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/TestLinuxContainerExecutorWithMocks.java
> 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: Sub-task
> Components: nodemanager
> Reporter: Zhijie Shen
> Assignee: Tsuyoshi OZAWA
> Fix For: 2.6.0
>
> Attachments: YARN-2013.1.patch, YARN-2013.2.patch,
> YARN-2013.3-2.patch, YARN-2013.3.patch, YARN-2013.4.patch, YARN-2013.5.patch
>
>
> 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)
