[ 
https://issues.apache.org/jira/browse/YARN-4751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eric Payne updated YARN-4751:
-----------------------------
    Attachment: YARH-4752-branch-2.7.002.patch

Attaching {{YARH-4752-branch-2.7.002.patch}}. It addresses some of the 
checkstyle warnings. The findbugs warning is regarding {{ZKRMStateStore}}, 
which version 001 of this patch didn't change. This false findbugs warning 
looks to be documented in YARN-4328.

Regarding unit tests, I have been trying to decide the best approach. I would 
like to start up a MiniYARNCluster in order to get as close to a labeled 
environment so that this patch can be tested. However, starting up a 
MiniYARNCluster, configuring multiple nodes, configuring multiple queues, 
configuring labels, and launching containers on both labeled and non-labeled 
queues will be a lot of testing overhead for a patch that will only be 
integrated into 2.7. There are a couple of unit tests that could be used as 
models, but I don't see anything that already does what would be needed.

[~sunilg] and [~jlowe], I would appreciate your opinion on the best unit test 
approach.

> In 2.7, Labeled queue usage not shown properly in capacity scheduler UI
> -----------------------------------------------------------------------
>
>                 Key: YARN-4751
>                 URL: https://issues.apache.org/jira/browse/YARN-4751
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: capacity scheduler, yarn
>    Affects Versions: 2.7.3
>            Reporter: Eric Payne
>            Assignee: Eric Payne
>         Attachments: 2.7 CS UI No BarGraph.jpg, 
> YARH-4752-branch-2.7.001.patch, YARH-4752-branch-2.7.002.patch
>
>
> In 2.6 and 2.7, the capacity scheduler UI does not have the queue graphs 
> separated by partition. When applications are running on a labeled queue, no 
> color is shown in the bar graph, and several of the "Used" metrics are zero.



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

Reply via email to