Peng Zhang commented on YARN-3111:

I think overlay is not a good choice. 
Currently scheduler bar is already overlay of steady share, instantaneous share 
and max resources. 
Then overlaying  two dimension of resources may generate 2 * 3 elements? If so, 
it should be too cluttered without new resources added.

When test this patch in our cluster, I found a new issue with some abnormal 
queue's bar width is decided by (queue steady resource / cluster resource), and 
queue's usage width is decided by (queue's usage resource / cluster resource). 
For above two percent computation, dominant resource may be different, so two 
percent value is still in different dimension, and it causes confusion.

To figure out above problem, we practice making queue's steady share 
proportional to root queue share in different resource dimension, so first 
percent value(queue steady resource / cluster resource) has the same percent 
value in different resources, and it will not cause confusion. 

I think deeper problem is that FS can configure cpu and memory seperately(eg: 
min resource, max resource ), and it makes resource not proportional between 
queues, but need a view of percentage.

> Fix ratio problem on FairScheduler page
> ---------------------------------------
>                 Key: YARN-3111
>                 URL: https://issues.apache.org/jira/browse/YARN-3111
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: fairscheduler
>    Affects Versions: 2.6.0
>            Reporter: Peng Zhang
>            Assignee: Peng Zhang
>            Priority: Minor
>         Attachments: YARN-3111.1.patch, YARN-3111.png
> Found 3 problems on FairScheduler page:
> 1. Only compute memory for ratio even when queue schedulingPolicy is DRF.
> 2. When min resources is configured larger than real resources, the steady 
> fair share ratio is so long that it is out the page.
> 3. When cluster resources is 0(no nodemanager start), ratio is displayed as 
> "NaN% used"
> Attached image shows the snapshot of above problems. 

This message was sent by Atlassian JIRA

Reply via email to