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

Zhijie Shen commented on YARN-2242:
-----------------------------------

Hi [~gtCarrera9], the useless ExitCodeException stack is not just limited to AM 
container. Given a container gets crashed, we're always expecting this message. 
Previously, I filed similar ticket: YARN-2013. [~ozawa], was working on it, but 
I didn't have a chance to look into it. Maybe you want to consolidate the two 
jiras.

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

Reply via email to