[YARN-10590] Consider legacy auto queue creation absolute resource template to avoid rounding errors

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.4.0
• Fix Version/s: 3.4.0
• Component/s: capacity scheduler
• Labels: pull-request-available
• Target Version/s: 3.4.0
• Hadoop Flags: Reviewed
• Assignee: Andras Gyori
• Reporter: Qi Zhu
• Created: 22/Jan/21 05:56
• Updated: 25/Jan/24 16:00
• Resolved: 22/Feb/22 11:28

Description

"Because as we discussed in YARN-10504 , the initialization of auto created queues from template was changed (see comment and comment)."

1. As the comment we discussed, we found the effective core is different(the gap), because the update effective  will override the absolute auto created leaf queue.

2. But actually, the new logic in YARN-10504 override is right, the difference is caused by test case , don't consider the calculation loss of multi resource type, the cap/absolute are all calculated by one type, (memory) in DefaultResourceCalculator, (dominant type) in DominantResourceCalculator. As we known in the comment, the absolute auto created leaf queue will merge the effective resource by cap/absolute calculated result, this caused the gap.

2. In other case(not absolute case) in the auto created leaf queue, the merge will not cause the gap, in update effective resource override will also use the one type calculated result. 

3. So this jira just make the test right, the calculation result is already right.

Issue Links

• links to: GitHub Pull Request #3868