[ https://issues.apache.org/jira/browse/YARN-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14481974#comment-14481974 ]
Hudson commented on YARN-3273: ------------------------------ FAILURE: Integrated in Hadoop-trunk-Commit #7516 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/7516/]) Move YARN-3273 from 2.8 to 2.7. (zjshen: rev 3fb5abfc87953377f86e06578518801a181d7697) * hadoop-yarn-project/CHANGES.txt > Improve web UI to facilitate scheduling analysis and debugging > -------------------------------------------------------------- > > Key: YARN-3273 > URL: https://issues.apache.org/jira/browse/YARN-3273 > Project: Hadoop YARN > Issue Type: Improvement > Reporter: Jian He > Assignee: Rohith > Fix For: 2.7.0 > > Attachments: 0001-YARN-3273-v1.patch, 0001-YARN-3273-v2.patch, > 0002-YARN-3273.patch, 0003-YARN-3273.patch, 0003-YARN-3273.patch, > 0004-YARN-3273.patch, YARN-3273-am-resource-used-AND-User-limit-v2.PNG, > YARN-3273-am-resource-used-AND-User-limit.PNG, > YARN-3273-application-headroom-v2.PNG, YARN-3273-application-headroom.PNG > > > Job may be stuck for reasons such as: > - hitting queue capacity > - hitting user-limit, > - hitting AM-resource-percentage > The first queueCapacity is already shown on the UI. > We may surface things like: > - what is user's current usage and user-limit; > - what is the AM resource usage and limit; > - what is the application's current HeadRoom; > -- This message was sent by Atlassian JIRA (v6.3.4#6332)