[YARN-5387] FairScheduler: add the ability to specify a parent queue to all placement rules

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Implemented
• Component/s: fairscheduler
• Labels: supportability
• Assignee: Wilfred Spiegelenburg
• Reporter: Wilfred Spiegelenburg
• Created: 15/Jul/16 08:25
• Updated: 26/Feb/20 05:29
• Resolved: 27/Mar/19 12:28

Description

In the current placement policy there all rules generate a queue name under the root. The only exception is the nestedUserQueue rule. This rule allows a queue to be created under a parent queue defined by a second rule.

Instead of creating new rules to also allow nested groups, secondary groups or nested queues for new rules that we think of we should generalise this by allowing a parent attribute to be specified in each rule like the create flag.

The optional parent attribute for a rule should allow the following values:

• empty (which is the same as not specifying the attribute)
• a rule
• a fixed value (with or without the root prefix)

Issue Links

• Is contained by: YARN-8967 Change FairScheduler to use PlacementRule interface
• relates to: YARN-6567 Flexible Workload Management