[YARN-8858] CapacityScheduler should respect maximum node resource when per-queue maximum-allocation is being used.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.10.0, 3.2.0, 2.9.2, 3.0.4, 3.1.2, 3.3.0, 2.8.6
• Target Version/s: 2.10.0, 3.2.0, 2.9.2, 3.0.4, 3.1.2, 2.8.6
• Assignee: Wangda Tan
• Reporter: Sumana Sathish
• Created: 09/Oct/18 05:37
• Updated: 06/Nov/18 06:44
• Resolved: 06/Nov/18 06:20

Description

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.

Issue Links

• is caused by: YARN-8720 CapacityScheduler does not enforce max resource allocation check at queue level