[
https://issues.apache.org/jira/browse/YARN-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14363418#comment-14363418
]
Hadoop QA commented on YARN-3273:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12704785/0002-YARN-3273.patch
against trunk revision 3da9a97.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 6 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:red}-1 findbugs{color}. The patch appears to introduce 5 new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:
org.apache.hadoop.yarn.server.resourcemanager.TestFifoScheduler
org.apache.hadoop.yarn.server.resourcemanager.webapp.TestNodesPage
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6973//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-YARN-Build/6973//artifact/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-resourcemanager.html
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6973//console
This message is automatically generated.
> 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
> Attachments: 0001-YARN-3273-v1.patch, 0001-YARN-3273-v2.patch,
> 0002-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)
