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

["Ruslan Dautkhanov (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/YARN-5387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16469101#comment-16469101 ] 

Ruslan Dautkhanov commented on YARN-5387:
-----------------------------------------

Hi [~wilfreds], 
Would this work cover cases like when we want to map a subset of users or secondary groups into a bigger bucket, and then map individual users into subbuckets there. In our organization, we have different departments use the same Hadoop cluster. So we'd like to define bigger buckets with those departments so we can cap a whole department first, and then individual users would still have their personal subqueues.
Something like, root.[department].users.[userid], where  [department] would be driven by a fixed list of secondary groups that make up a department. If secondary group is not an option, we could put a list of users for each department. 
Other use case for us, is when we have a subset of users that should go to a "production" queue root.prod.[userid] vs rest of users going into root.users.[userid] - we could route manually certain service accounts into root.prod resource pool instead of going to default root.users.. 
Thanks!

> FairScheduler: add the ability to specify a parent queue to all placement rules
> -------------------------------------------------------------------------------
>
>                 Key: YARN-5387
>                 URL: https://issues.apache.org/jira/browse/YARN-5387
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: fairscheduler
>            Reporter: Wilfred Spiegelenburg
>            Assignee: Wilfred Spiegelenburg
>            Priority: Major
>              Labels: supportability
>
> 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)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org