hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Li Lu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-2242) Improve exception information on AM launch crashes
Date Tue, 08 Jul 2014 17:56:06 GMT

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

Li Lu updated YARN-2242:
------------------------

    Attachment: YARN-2242-070814.patch

New patch to add the swallowed diagnostics information back, also reformatted the exception
output for easy understanding. Now the exception output contains all original exception information,
also a pointer to the logs. Addressed [~stevel@apache.org]'s null URL issue by adding one
more branch. 

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