You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2015/09/23 23:35:06 UTC
[jira] [Commented] (YARN-3544) AM logs link missing in the RM UI
for a completed app
[ https://issues.apache.org/jira/browse/YARN-3544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14905307#comment-14905307 ]
Hudson commented on YARN-3544:
------------------------------
FAILURE: Integrated in Hadoop-trunk-Commit #8505 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/8505/])
CHANGES.txt: Moving YARN-1884, YARN-3171, YARN-3740, YARN-3248, YARN-3544 to 2.6.1 given the backport. (vinodkv: rev f3e5bc67661ebc7e14509f2a267131ae314699dc)
* hadoop-yarn-project/CHANGES.txt
> 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
> Labels: 2.6.1-candidate
> Fix For: 2.6.1, 2.7.1
>
> Attachments: Screen Shot 2015-04-27 at 6.24.05 PM.png, YARN-3544-branch-2.6.1.txt, YARN-3544-branch-2.7-1.2.patch, YARN-3544-branch-2.7-1.patch, 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)