[
https://issues.apache.org/jira/browse/YARN-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15634527#comment-15634527
]
Konstantinos Karanasos commented on YARN-2995:
----------------------------------------------
Regarding the remaining issues:
* The checkstyle issue is about a method that takes more than 7 parameters in
one of the test classes. That was already the case for that method; I just
added some more parameters.
* The javadoc issue, as I already explained in a comment above, is related to
Java 8 complaining about using '_' as identifiers. This is used in multiple
places in the Web UI classes, and should be treated in a separate JIRA.
* The unit test issue regarding {{TestQueuingContainerManager}} is unrelated to
the present JIRA and is tracked in YARN-5377.
* There is a build issue in sls when running the corresponding tests, but it
might be a Jenkins issue, since it builds fine for me locally. Just kicked-off
Jenkins again to see if the problem persists.
> Enhance UI to show cluster resource utilization of various container types
> --------------------------------------------------------------------------
>
> Key: YARN-2995
> URL: https://issues.apache.org/jira/browse/YARN-2995
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Reporter: Sriram Rao
> Assignee: Konstantinos Karanasos
> Priority: Blocker
> Attachments: YARN-2995.001.patch, YARN-2995.002.patch,
> YARN-2995.003.patch, YARN-2995.004.patch, all-nodes.png, all-nodes.png,
> opp-container.png
>
>
> This JIRA proposes to extend the Resource manager UI to show how cluster
> resources are being used to run *guaranteed start* and *queueable*
> containers. For example, a graph that shows over time, the fraction of
> running containers that are *guaranteed start* and the fraction of running
> containers that are *queueable*.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
