[
https://issues.apache.org/jira/browse/YARN-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14054672#comment-14054672
]
Zhijie Shen commented on YARN-2242:
-----------------------------------
bq. There's nothing in the Application Report that appears to publish this
path. Is this the case? If so I'll add a new JIRA
We have provided ContainerReport, where there's a log url, point to the web UI
of the timeline server that serves the aggregated log. To make it work, you
need to bring up the timeline server and enable the generic history service.
> 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)
