[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=14905744#comment-14905744 ] Hudson commented on YARN-3544: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #2348 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/2348/]) 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)
[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=14905695#comment-14905695 ] Hudson commented on YARN-3544: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #2375 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2375/]) 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)
[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=14905626#comment-14905626 ] Hudson commented on YARN-3544: -- FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #409 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/409/]) 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)
[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=14905521#comment-14905521 ] Hudson commented on YARN-3544: -- SUCCESS: Integrated in Hadoop-Yarn-trunk #1169 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/1169/]) 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)
[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=14905414#comment-14905414 ] Hudson commented on YARN-3544: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #429 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/429/]) 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)
[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=14905341#comment-14905341 ] Hudson commented on YARN-3544: -- FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #436 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/436/]) 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)
[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)
[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=14523342#comment-14523342 ] Hudson commented on YARN-3544: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk #2130 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2130/]) YARN-3544. Got back AM logs link on the RM web UI for a completed app. Contributed by Xuan Gong. (zjshen: rev 7e8639fda40c13fe163128d7a725fcd0f2fce3c5) * hadoop-yarn-project/CHANGES.txt * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/RMAppBlock.java > 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 > Fix For: 2.7.1 > > Attachments: Screen Shot 2015-04-27 at 6.24.05 PM.png, > 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)
[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=14523298#comment-14523298 ] Hudson commented on YARN-3544: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #181 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/181/]) YARN-3544. Got back AM logs link on the RM web UI for a completed app. Contributed by Xuan Gong. (zjshen: rev 7e8639fda40c13fe163128d7a725fcd0f2fce3c5) * hadoop-yarn-project/CHANGES.txt * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/RMAppBlock.java > 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 > Fix For: 2.7.1 > > Attachments: Screen Shot 2015-04-27 at 6.24.05 PM.png, > 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)
[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=14523089#comment-14523089 ] Hudson commented on YARN-3544: -- FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #171 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/171/]) YARN-3544. Got back AM logs link on the RM web UI for a completed app. Contributed by Xuan Gong. (zjshen: rev 7e8639fda40c13fe163128d7a725fcd0f2fce3c5) * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/RMAppBlock.java * 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 > Fix For: 2.7.1 > > Attachments: Screen Shot 2015-04-27 at 6.24.05 PM.png, > 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)
[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=14523078#comment-14523078 ] Hudson commented on YARN-3544: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #2112 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/2112/]) YARN-3544. Got back AM logs link on the RM web UI for a completed app. Contributed by Xuan Gong. (zjshen: rev 7e8639fda40c13fe163128d7a725fcd0f2fce3c5) * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/RMAppBlock.java * 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 > Fix For: 2.7.1 > > Attachments: Screen Shot 2015-04-27 at 6.24.05 PM.png, > 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)
[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=14523032#comment-14523032 ] Hudson commented on YARN-3544: -- FAILURE: Integrated in Hadoop-Yarn-trunk #914 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/914/]) YARN-3544. Got back AM logs link on the RM web UI for a completed app. Contributed by Xuan Gong. (zjshen: rev 7e8639fda40c13fe163128d7a725fcd0f2fce3c5) * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/RMAppBlock.java * 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 > Fix For: 2.7.1 > > Attachments: Screen Shot 2015-04-27 at 6.24.05 PM.png, > 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)
[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=14523023#comment-14523023 ] Hudson commented on YARN-3544: -- FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #180 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/180/]) YARN-3544. Got back AM logs link on the RM web UI for a completed app. Contributed by Xuan Gong. (zjshen: rev 7e8639fda40c13fe163128d7a725fcd0f2fce3c5) * hadoop-yarn-project/CHANGES.txt * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/RMAppBlock.java > 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 > Fix For: 2.7.1 > > Attachments: Screen Shot 2015-04-27 at 6.24.05 PM.png, > 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)
[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=14522170#comment-14522170 ] Hudson commented on YARN-3544: -- FAILURE: Integrated in Hadoop-trunk-Commit #7707 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/7707/]) YARN-3544. Got back AM logs link on the RM web UI for a completed app. Contributed by Xuan Gong. (zjshen: rev 7e8639fda40c13fe163128d7a725fcd0f2fce3c5) * hadoop-yarn-project/CHANGES.txt * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/RMAppBlock.java > 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 > Fix For: 2.7.1 > > Attachments: Screen Shot 2015-04-27 at 6.24.05 PM.png, > 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)
[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=14522150#comment-14522150 ] Zhijie Shen commented on YARN-3544: --- Verified 2.7 branch patch. It works fine too. Will commit it. > 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-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)
[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=14521802#comment-14521802
]
Hadoop QA commented on YARN-3544:
-
\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | pre-patch | 14m 0s | Pre-patch branch-2.7
compilation is healthy. |
| {color:green}+1{color} | @author | 0m 0s | The patch does not contain any
@author tags. |
| {color:red}-1{color} | tests included | 0m 0s | The patch doesn't appear
to include any new or modified tests. Please justify why no new tests are
needed for this patch. Also please list what manual steps were performed to
verify this patch. |
| {color:green}+1{color} | whitespace | 0m 0s | The patch has no lines that
end in whitespace. |
| {color:red}-1{color} | patch | 0m 0s | The patch command could not apply
the patch. |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL |
http://issues.apache.org/jira/secure/attachment/12729519/YARN-3544-branch-2.7-1.2.patch
|
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | branch-2.7 / 185a1ff |
| Console output |
https://builds.apache.org/job/PreCommit-YARN-Build/7555/console |
This message was automatically generated.
> 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-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)
[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=14521759#comment-14521759 ] Xuan Gong commented on YARN-3544: - bq. One nit: maybe we should place createApplicationAttemptTable before clarifyAppState to minimize diff. DONE > 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-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)
[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=14520859#comment-14520859
]
Zhijie Shen commented on YARN-3544:
---
Thanks for creating the branch-2.7 patch. One nit: maybe we should place
{{createApplicationAttemptTable}} before {{clarifyAppState}} to minimize diff.
> 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-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)
[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=14520680#comment-14520680
]
Hadoop QA commented on YARN-3544:
-
\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | pre-patch | 14m 4s | Pre-patch branch-2.7
compilation is healthy. |
| {color:green}+1{color} | @author | 0m 0s | The patch does not contain any
@author tags. |
| {color:red}-1{color} | tests included | 0m 0s | The patch doesn't appear
to include any new or modified tests. Please justify why no new tests are
needed for this patch. Also please list what manual steps were performed to
verify this patch. |
| {color:green}+1{color} | whitespace | 0m 0s | The patch has no lines that
end in whitespace. |
| {color:red}-1{color} | patch | 0m 0s | The patch command could not apply
the patch. |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL |
http://issues.apache.org/jira/secure/attachment/12729366/YARN-3544-branch-2.7-1.patch
|
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | branch-2.7 / 6ac2b57 |
| Console output |
https://builds.apache.org/job/PreCommit-YARN-Build/7548/console |
This message was automatically generated.
> 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-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)
[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=14520663#comment-14520663 ] Xuan Gong commented on YARN-3544: - bq. the patch doesn't apply for branch-2.7. It seems to be non-trivial conflict merge. Would you please take a look? Uploaded a new patch for branch-2.7. > 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-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)
[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=14520586#comment-14520586 ] Zhijie Shen commented on YARN-3544: --- [~xgong], the patch doesn't apply for branch-2.7. It seems to be non-trivial conflict merge. Would you please take a look? > 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)
[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=14520425#comment-14520425 ] Zhijie Shen commented on YARN-3544: --- bq. Doesnt the NM log link redirect the log server after the logs have been aggregated? Thanks, Hitesh! I didn't notice this option before. Tried it locally, and the whole process of the completed log is working fine now. Will commit the patch late today unless there's further comment. > 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)
[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=14520379#comment-14520379 ] Hitesh Shah commented on YARN-3544: --- I meant "redirect to the log server" > 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)
[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=14520378#comment-14520378 ] Hitesh Shah commented on YARN-3544: --- Doesnt the NM log link redirect the log server after the logs have been aggregated? > 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)
[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=14520365#comment-14520365 ] Zhijie Shen commented on YARN-3544: --- Xuan, thanks for the patch. I've tried your patch locally, and it brought the content back to the web UI. However, I've one concern. It seems that the link to the local log on NM is not useful after the app is finished, because the log is not supposed to be there any longer. So is this jira supposed to fix the regression, or ultimately provide a useful link to AM container log? Those seem to be different goals. /cc [~hitesh] > 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)
[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=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)
[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=14516138#comment-14516138 ] Xuan Gong commented on YARN-3544: - This is the web ui changes. That is why I do not add any test cases. Uploaded the app wen ui screenshot for a killed job after the patch is applied > 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)
[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=14515167#comment-14515167 ] Vinod Kumar Vavilapalli commented on YARN-3544: --- Can you add a test-case? > 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: 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)
[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=14512205#comment-14512205
]
Hadoop QA commented on YARN-3544:
-
\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | pre-patch | 14m 38s | Pre-patch trunk compilation is
healthy. |
| {color:green}+1{color} | @author | 0m 0s | The patch does not contain any
@author tags. |
| {color:red}-1{color} | tests included | 0m 0s | The patch doesn't appear
to include any new or modified tests. Please justify why no new tests are
needed for this patch. Also please list what manual steps were performed to
verify this patch. |
| {color:green}+1{color} | whitespace | 0m 0s | The patch has no lines that
end in whitespace. |
| {color:green}+1{color} | javac | 7m 32s | There were no new javac warning
messages. |
| {color:green}+1{color} | javadoc | 9m 34s | There were no new javadoc
warning messages. |
| {color:green}+1{color} | release audit | 0m 22s | The applied patch does
not increase the total number of release audit warnings. |
| {color:red}-1{color} | checkstyle | 7m 40s | The applied patch generated 1
additional checkstyle issues. |
| {color:green}+1{color} | install | 1m 33s | mvn install still works. |
| {color:green}+1{color} | eclipse:eclipse | 0m 32s | The patch built with
eclipse:eclipse. |
| {color:green}+1{color} | findbugs | 1m 15s | The patch does not introduce
any new Findbugs (version 2.0.3) warnings. |
| {color:red}-1{color} | yarn tests | 54m 43s | Tests failed in
hadoop-yarn-server-resourcemanager. |
| | | 97m 52s | |
\\
\\
|| Reason || Tests ||
| Failed unit tests |
hadoop.yarn.server.resourcemanager.applicationsmanager.TestAMRestart |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL |
http://issues.apache.org/jira/secure/attachment/12728109/YARN-3544.1.patch |
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / 78c6b46 |
| checkstyle |
https://builds.apache.org/job/PreCommit-YARN-Build/7498/artifact/patchprocess/checkstyle-result-diff.txt
|
| hadoop-yarn-server-resourcemanager test log |
https://builds.apache.org/job/PreCommit-YARN-Build/7498/artifact/patchprocess/testrun_hadoop-yarn-server-resourcemanager.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-YARN-Build/7498/testReport/ |
| Console output |
https://builds.apache.org/job/PreCommit-YARN-Build/7498/console |
This message was automatically generated.
> 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: Critical
> Attachments: 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)
