Wangda Tan created YARN-8858:
--------------------------------
Summary: CapacityScheduler should respect maximum node resource
when per-queue maximum-allocation is being used.
Key: YARN-8858
URL: https://issues.apache.org/jira/browse/YARN-8858
Project: Hadoop YARN
Issue Type: Bug
Reporter: Sumana Sathish
Assignee: Wangda Tan
This issue happens after YARN-8720.
Before that, AMS uses scheduler.getMaximumAllocation to do the normalization.
After that, AMS uses LeafQueue.getMaximumAllocation. The scheduler one uses
nodeTracker.getMaximumAllocation, but the LeafQueue.getMaximum doesn't.
We should use the scheduler.getMaximumAllocation to cap the per-queue's
maximum-allocation every time.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
