[ 
https://issues.apache.org/jira/browse/YARN-3362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14366191#comment-14366191
 ] 

Wangda Tan commented on YARN-3362:
----------------------------------

My proposal is:

For now, RM CapacityScheduler UI looks like
{code}
+ root [==========================] 50% used
  + a  [=======================================] 75% used
    - a1 [=================]  30% used
      ---------------------------------------------
      |          Queue Metrics Table               |
      |--------------------------------------------|
      |       metrics1       |            value1   |
      |       metrics2       |            value2   |
      |       metrics3       |            value3   |
      |       metrics4       |            value4   |
      ----------------------------------------------
  + b [...]
  + c [...]
{code}

We can add one more hierarchy above queue's hierarchy, which are labels can be 
accessed and/or labels are being used by the queue, which can looks like

{code}
+ label_x  [=====================] 30% used
        + root [=====================] 30% used
          + a  [=======================================] 75% used
            + a1 [=================]  30% used
              ---------------------------------------------
              |          Queue Metrics Table (For label_x) |
              |--------------------------------------------|
              |       metrics1       |            value1   |
              |       metrics2       |            value2   |
              |       metrics3       |            value3   |
              |       metrics4       |            value4   |
              ----------------------------------------------
+ label_y
    + root [...]
    + ...
+ label_z
    + root [...]
    + ...
+ no_label
    + root [...]
    + ...
{code}

To make it backward compatible, when there's no label in the system, it will 
not show "label-bar", and root is still "root-queue".

Please feel free to share your ideas on this!

> Add node label usage in RM CapacityScheduler web UI
> ---------------------------------------------------
>
>                 Key: YARN-3362
>                 URL: https://issues.apache.org/jira/browse/YARN-3362
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: capacityscheduler, resourcemanager, webapp
>            Reporter: Wangda Tan
>
> We don't have node label usage in RM CapacityScheduler web UI now, without 
> this, user will be hard to understand what happened to nodes have labels 
> assign to it.



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

Reply via email to