[YARN-10169] Mixed absolute resource value and percentage-based resource value in CapacityScheduler should fail

• Type: Bug
• Status: Patch Available
• Priority: Blocker
• Resolution: Unresolved
• Assignee: Qi Zhu
• Reporter: Wangda Tan
• Created: 27/Feb/20 00:51
• Updated: 18/Dec/20 01:49

Description

To me this is a bug: if there's a queue has capacity set to float, and maximum-capacity set to absolute value. Existing logic allows the behavior.

For example:

queue.capacity = 0.8 
queue.maximum-capacity = [mem=x, vcore=y] 

We should throw exception when configured like this.

Issue Links

• is blocked by: YARN-10496 [Umbrella] Support Flexible Auto Queue Creation in Capacity Scheduler