hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (YARN-2242) Improve exception information on AM launch crashes
Date Fri, 04 Jul 2014 18:51:34 GMT

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

Vinod Kumar Vavilapalli reopened YARN-2242:
-------------------------------------------


This is not the right solution - you are swallowing diagnostics from the container. Imagine
AM container failing due to localization failure, we want to show the right diagnostics there.
The solution for this ticket is to change the message on the NM side, not the RM side.

Reopening this ticket..

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

Mime
View raw message