[
https://issues.apache.org/jira/browse/YARN-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14004968#comment-14004968
]
Ashwin Shankar commented on YARN-2012:
--------------------------------------
[~sandyr] Thanks for looking into this.
bq. I think it's a little confusing for the rule to fall back to "default". Can
we let this part be handled by the "create" logic in assignAppToQueue?
Sure but just to clarify,are you saying that in
QueuePlacementRule.assignAppToQueue we should return "root.default" if the
queue returned by Default rule is not configured and if create is false ? ie
Basically, in the "create" logic, we won't cause a skip to occur if the rule is
a Default rule, instead we return root.default.
> Fair Scheduler : Default rule in queue placement policy can take a queue as
> an optional attribute
> -------------------------------------------------------------------------------------------------
>
> Key: YARN-2012
> URL: https://issues.apache.org/jira/browse/YARN-2012
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: scheduler
> Reporter: Ashwin Shankar
> Assignee: Ashwin Shankar
> Labels: scheduler
> Attachments: YARN-2012-v1.txt, YARN-2012-v2.txt
>
>
> Currently 'default' rule in queue placement policy,if applied,puts the app in
> root.default queue. It would be great if we can make 'default' rule
> optionally point to a different queue as default queue . This queue should be
> an existing queue,if not we fall back to root.default queue hence keeping
> this rule as terminal.
> This default queue can be a leaf queue or it can also be an parent queue if
> the 'default' rule is nested inside nestedUserQueue rule(YARN-1864).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
