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-2242) Improve exception information on AM launch crashes
Date Wed, 09 Jul 2014 17:47:05 GMT

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

Hadoop QA commented on YARN-2242:
---------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12654839/YARN-2242-070814-1.patch
  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 1 new or modified
test files.

    {color:red}-1 javac{color:red}.  The patch appears to cause the build to fail.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4239//console

This message is automatically generated.

> Improve exception information on AM launch crashes
> --------------------------------------------------
>
>                 Key: YARN-2242
>                 URL: https://issues.apache.org/jira/browse/YARN-2242
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Li Lu
>            Assignee: Li Lu
>             Fix For: 2.6.0
>
>         Attachments: YARN-2242-070115-2.patch, YARN-2242-070814-1.patch, YARN-2242-070814.patch
>
>
> Now on each time AM Container crashes during launch, both the console and the webpage
UI only report a ShellExitCodeExecption. This is not only unhelpful, but sometimes confusing.
With the help of log aggregator, container logs are actually aggregated, and can be very helpful
for debugging. One possible way to improve the whole process is to send a "pointer" to the
aggregated logs to the programmer when reporting exception information. 



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

Mime
View raw message