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 Sat, 12 Jul 2014 04:40:05 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-071114.patch

Updated patch according to [~djp]'s review. Updated the interface of verifyAMCrashAtAllocatedDiagnosticInfo,
added a flag for checking included URL. Updated verifyAMCrashAtAllocatedDiagnosticInfo, checking
application attempt id and exit code.

> 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,
YARN-2242-071114.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