Naganarasimha G R commented on YARN-3362:

Thanks for the comment [~Wangda],
This idea is also good but i can think of few issues here 
* In most cases Queue hierarchy will be collapsed so the space between non leaf 
queue name and the bar might not look good 
* Bigger the name of the leaf queues more space between the queue name and the 
bar (at the upper level queues)
* Space based calculation might not work out so implementing it with Hammock 
might be little complex. 
* Here were you thinking of publishing absolute usage or usage @ queue level, I 
feel absolute usage would be better (YARN-3638 also suggest it), but existing 
shows just usage @ queue level.

Also i feel these modifications can take time, if this jira is important then 
we can push this in and we can further discuss about UI enhancements in another 
jira. thoughts?

> 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, 2015.05.12_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, 
> YARN-3362.20150512-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