hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsuyoshi OZAWA (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-2013) The diagnostics is always the ExitCodeException stack when the container crashes
Date Sun, 20 Jul 2014 11:24:39 GMT

     [ https://issues.apache.org/jira/browse/YARN-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tsuyoshi OZAWA updated YARN-2013:
---------------------------------

    Attachment: YARN-2013.5.patch

[~djp], thank you for review! Updated a patch to address your comment.

> 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
>         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)

Mime
View raw message