[YARN-8917] Absolute (maximum) capacity of level3+ queues is wrongly calculated for absolute resource

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 3.2.1
• Fix Version/s: 3.3.0, 3.2.1
• Component/s: capacityscheduler
• Target Version/s: 3.2.1
• Hadoop Flags: Reviewed
• Assignee: Tao Yang
• Reporter: Tao Yang
• Created: 19/Oct/18 09:33
• Updated: 27/Aug/19 02:36
• Resolved: 26/Aug/19 16:05

Description

Absolute capacity should be equal to multiply capacity by parent-queue's absolute-capacity,
but currently it's calculated as dividing capacity by parent-queue's absolute-capacity.
Calculation for absolute-maximum-capacity has the same problem.

For example: 
root.a   capacity=0.4   maximum-capacity=0.8
root.a.a1   capacity=0.5  maximum-capacity=0.6
Absolute capacity of root.a.a1 should be 0.2 but is wrongly calculated as 1.25
Absolute maximum capacity of root.a.a1 should be 0.48 but is wrongly calculated as 0.75

Moreover:
childQueue.getQueueCapacities().getCapacity()  should be changed to childQueue.getQueueCapacities().getCapacity(label) to avoid getting wrong capacity from default partition when calculating for a non-default partition.

Issue Links

• duplicates: YARN-9020 AbsoluteCapacity is wrongly set when call ParentQueue#setAbsoluteCapacity