[YARN-10930] Introduce universal configured capacity vector

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.4.0
• Component/s: capacity scheduler
• Labels: pull-request-available
• Hadoop Flags: Reviewed
• Assignee: Andras Gyori
• Reporter: Andras Gyori
• Created: 31/Aug/21 10:09
• Updated: 22/Oct/21 15:41
• Resolved: 22/Oct/21 15:34

Description

The proposal is to introduce a capacity resource vector that is universally parsed for every queue. CapacityResourceVector is a way to unite the current capacity modes (weight, percentage, absolute), while maintaining flexibility and extendability.
CapacityResourceVector is a good fit for the existing capacity configs, for example:

• percentage mode: root.example.capacity 50 is a syntactic sugar for [memory=50%, vcores=50%, ....]
• absolute mode: root.example.capacity [memory=1024, vcores=2] is a natural fit for the vector, there is no need for additional settings
  CapacityResourceVector will be used in a future refactor, to unify the resource calculation and lift the limitation imposed on the queue hierarchy capacity settings (eg. can not use both absolute resource and percentage in the same hierarchy etc...)

Issue Links

• links to: GitHub Pull Request #3358