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

Jason Lowe commented on YARN-3638:
----------------------------------

Ah, got it.  I originally thought the complaint was the user cannot find that 
information anywhere on the scheduler page, but it is there for all the leaf 
queues (in the details accessed by the twisty to the left of the queue).  I'm 
OK with having the percentage to the right of the queue bar being an absolute 
used percentage as long as it's clear that's what it is representing.  
Otherwise I can already see the JIRA stating the percentage shown to the right 
of the queue doesn't match the relative length of the bars to their capacity.  
;-)


> Yarn Resource Manager Scheduler page - show percentage of total cluster that 
> each queue is using
> ------------------------------------------------------------------------------------------------
>
>                 Key: YARN-3638
>                 URL: https://issues.apache.org/jira/browse/YARN-3638
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: capacityscheduler, resourcemanager, scheduler, yarn
>    Affects Versions: 2.6.0
>         Environment: HDP 2.2
>            Reporter: Hari Sekhon
>            Priority: Minor
>
> Request to show % of total cluster resources each queue is currently 
> consuming for jobs on the Yarn Resource Manager Scheduler page.
> Currently the Yarn Resource Manager Scheduler page shows the % of total used 
> for root queue and the % of each given queue's configured capacity that is 
> used (often showing say 150% if the max capacity is greater than configured 
> capacity to allow bursting where there are free resources). This is fine, but 
> it would be good to additionally show the % of total cluster that each given 
> queue is consuming and not just the % of that queue's configured capacity.



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

Reply via email to