Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Fri, 4 Jul 2014 18:51:34 +0000 (UTC)
From: "Vinod Kumar Vavilapalli (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12724850.1404260454331.5581.1404499894457@arcas>
In-Reply-To: <JIRA.12724850.1404260454331@arcas>
References: <JIRA.12724850.1404260454331@arcas>
Subject: [jira] [Commented] (YARN-2242) Improve exception information on AM
 launch crashes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Vinod Kumar Vavilapalli commented on YARN-2242:
-----------------------------------------------

In a way, YARN-2013 was on the right track. We need to close one of these as a dup of the other and put in the right fix..

> 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-070114-1.patch, YARN-2242-070114.patch, YARN-2242-070115-1.patch, YARN-2242-070115-2.patch, YARN-2242-070115.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)