hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peng Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3111) Fix ratio problem on FairScheduler page
Date Wed, 18 Mar 2015 04:11:39 GMT

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

Peng Zhang commented on YARN-3111:

Thanks for your advices

For 4 proposal listed above:
1 & 2 are already done in the patch
3 is good, but one question is that parent queue has no tooltip now, but it has its own bar.
And think over 3 & 4, what about listing all resources's usage percent on the text on
the right of each bar? Maybe color red for dominant resource? or just judge it by comparing
percent number?

And also what do you think of the issue I mentioned above? I think it still can happen after
1 & 2, cause for one queue: steady, fair, max, usage resource may have different dominant
resource type. If I make a mistake here, please let me know.
bq. 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.

> 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

View raw message