Wangda Tan commented on YARN-3362:

Hi Naga,
Thanks for updating,

1) To your questions: 
You can refer to YARN-2824 for more information about why default cap of 
labeled resource set to zero.
The default of max-cap is 100 because queue can use such resource without 
configure it.  Let me know if you have more questions.

2) About showing resources of partitions, I think it's very helpful. I think 
you can include used-resource of each partition as well, You can file a 
separate ticket if it is hard to be added with this ticket.

3) About "Hide Hierarchy", I think it's good for queue capacity comparison, but 
admin may get confused after checked "Hide Hierarchy", it's better to be added 
to some other places instead of modify queue UI itself.

> 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
>            Assignee: Naganarasimha G R
>         Attachments: 2015.05.06 Folded Queues.png, 2015.05.06 Queue 
> Expanded.png, 2015.05.07_3362_Queue_Hierarchy.png, 
> 2015.05.10_3362_Queue_Hierarchy.png, CSWithLabelsView.png, 
> No-space-between-Active_user_info-and-next-queues.png, Screen Shot 2015-04-29 
> at 11.42.17 AM.png, YARN-3362.20150428-3-modified.patch, 
> YARN-3362.20150428-3.patch, YARN-3362.20150506-1.patch, 
> YARN-3362.20150507-1.patch, YARN-3362.20150510-1.patch, 
> YARN-3362.20150511-1.patch, capacity-scheduler.xml
> 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

Reply via email to