Ashwin Shankar commented on YARN-3111:
I dont think 1 is done in the patch. My bad, I wasn't clear. In 1 what I was
suggesting was that - "represent that resource of steady/instant/max on the bar
which is dominant in usage or used resources", so that,
steady/instant/max/usage on the bar all finally represent ONE dimension in that
bar/queue. So lets say usage of the queue is (20% mem, 60 % vcore), then
steady/instant/max/usage would all display only vcore.
bq. 3 is good, but one question is that parent queue has no tooltip now, but it
has its own bar.
Parent queues(except root) have a tooltip, I just checked in trunk. Can you
check again ?
bq. 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?
It would be nice to have that with the color, however I'm concerned that it
might look ugly from UE perspective.
bq. 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
I believe this is clarified in the first paragraph of this comment. Let me know
if you still have this concern.
> 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