[
https://issues.apache.org/jira/browse/YARN-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13699488#comment-13699488
]
Zhijie Shen commented on YARN-675:
----------------------------------
Checked YarnClient and found one issue: ContainerId is not directly accessible
from the aspect of YarnClient. Correct me if I'm wrong here.
One way to walk around is to use the RESTful API to request either AppInfo or
AppAttemptInfo from RMWebServices. It contains the url to the AM container log.
Then, we can use this url to pull the log.
Currently, this url is pointing to a webpage. After YARN-649 gets fixed, I'd
like to update it to pointing the RESTful API of obtaining the container log,
because IMHO, it's enough for the DAO object to just hold the log content,
which is independent of rendering.
Thoughts, please.
> In YarnClient, pull AM logs on AM container failure
> ---------------------------------------------------
>
> Key: YARN-675
> URL: https://issues.apache.org/jira/browse/YARN-675
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: client
> Affects Versions: 2.0.4-alpha
> Reporter: Sandy Ryza
> Assignee: Zhijie Shen
>
> Similar to MAPREDUCE-4362, when an AM container fails, it would be helpful to
> pull its logs from the NM to the client so that they can be displayed
> immediately to the user.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
