hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhijie Shen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-675) In YarnClient, pull AM logs on AM container failure
Date Wed, 03 Jul 2013 22:39:20 GMT

    [ https://issues.apache.org/jira/browse/YARN-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13699538#comment-13699538

Zhijie Shen commented on YARN-675:

It's feasible to pass ContainerId through ApplicationReport, but I'm a bit conservative of
doing API change at this point, specially when the ContainerId is added only for pulling the
log. How do you think?

[~sandyr], BTW, the URL to the container log is constructed in AppInfo/AppAttemptInfo somewhat
differently from what is done in YARN-649.

            String url = join(HttpConfig.getSchemePrefix(),
                "/node", "/containerlogs/",
                "/", app.getUser());

user is part of the url. If this is adopted, there's no need to get the user through request.getRemoteUser()
> 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

View raw message