hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xuan Gong (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3544) AM logs link missing in the RM UI for a completed app
Date Wed, 29 Apr 2015 19:06:08 GMT

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

Xuan Gong commented on YARN-3544:
---------------------------------

Original, we are calling getContainerReport to AMContainer information (such as container
log url, nm address, startTime, etc). It works fine when the Application is running, and the
container is running. But when the application is finished, we will not keep finished container
info. In that case, we could not get any finished container report from RM. That is why we
see the AM logs link in web ui as "N/A" as well as other related attempt information.

In this patch, instead of querying from container Report, we directly get attempt(AM Container)
information from AttemptInfo which is from RMAttempt. So, no matter the application is running
or is finished, we could get related information and show them in the web ui

> AM logs link missing in the RM UI for a completed app 
> ------------------------------------------------------
>
>                 Key: YARN-3544
>                 URL: https://issues.apache.org/jira/browse/YARN-3544
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>    Affects Versions: 2.7.0
>            Reporter: Hitesh Shah
>            Assignee: Xuan Gong
>            Priority: Blocker
>         Attachments: Screen Shot 2015-04-27 at 6.24.05 PM.png, YARN-3544.1.patch
>
>
> AM log links should always be present ( for both running and completed apps).
> Likewise node info is also empty. This is usually quite crucial when trying to debug
where an AM was launched and a pointer to which NM's logs to look at if the AM failed to launch.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message