[
https://issues.apache.org/jira/browse/YARN-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14365837#comment-14365837
]
Karthik Kambatla commented on YARN-3111:
----------------------------------------
bq. Then overlaying two dimension of resources may generate 2 * 3 elements? If
so, it should be too cluttered without new resources added.
You are right. Let us not over-clutter it.
Ashwin's proposal sounds reasonable to me. Let us do 1 - 3 in this JIRA, and
may be 4 in a follow-up? For 4, what do you guys think of just listing the
usage of all resources, and may be labeling the dominant one dominant.
Otherwise, users will have to look at both places to get the complete picture.
> 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
(v6.3.4#6332)
