[YARN-10254] CapacityScheduler incorrect User Group Mapping after leaf queue change

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.4.0, 3.3.1
• Fix Version/s: 3.4.0, 3.3.1
• Component/s: capacity scheduler
• Target Version/s: 3.4.0, 3.3.1
• Hadoop Flags: Reviewed
• Assignee: Gergely Pollák
• Reporter: Gergely Pollák
• Created: 30/Apr/20 15:12
• Updated: 11/Feb/24 12:43
• Resolved: 02/Jun/20 16:34

Description

YARN-9879 and YARN-10198 introduced some major changes to user group mapping, and some of them unfortunately had some negative impact on the way mapping works.

In some cases incorrect PlacementContexts were created, where full queue path was passed as leaf queue name. This affects how the yarn cli app list displays the queues.

u:%user:%primary_group.%user mapping fails with an incorrect validation error when the %primary_group parent queue was a managed parent.

Group based rules in certain cases are mapped to root.[primary_group] rules, loosing the ability to create deeper structures.

 

Issue Links

• blocks: YARN-10108 FS-CS converter: nestedUserQueue with default rule results in invalid queue mapping