hadoop-yarn-issues mailing list archives

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

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

Hadoop QA commented on YARN-2013:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 2 new or modified
test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new Findbugs (version
2.0.3) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:red}-1 core tests{color}.  The patch failed these unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager:


    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-YARN-Build/4374//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4374//console

This message is automatically generated.

> 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

This message was sent by Atlassian JIRA

View raw message