[
https://issues.apache.org/jira/browse/YARN-1392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13821950#comment-13821950
]
Alejandro Abdelnur commented on YARN-1392:
------------------------------------------
a few final minor things:
* documentation, we should explicitly state that if the specified queue is
'default' it is handled as if no queue has been specified. This behavior is to
provide backwards compatibility with how Map-Reduce handles queue setting.
* FairScheduler.java, the original logic to map a user to queue if no placement
policy is defined seems it could be modeled as a default placement policy
rule(s). Then queue resolution is always done by the queue manager. there is a
false change (trimming empty line in line 715 after patch)
* QueuePlacementPolicy.java, 'primarygroup' rule should be 'primaryGroup' for
consistency (update doc as well)
> Allow sophisticated app-to-queue placement policies in the Fair Scheduler
> -------------------------------------------------------------------------
>
> Key: YARN-1392
> URL: https://issues.apache.org/jira/browse/YARN-1392
> Project: Hadoop YARN
> Issue Type: New Feature
> Components: scheduler
> Affects Versions: 2.2.0
> Reporter: Sandy Ryza
> Assignee: Sandy Ryza
> Attachments: YARN-1392-1.patch, YARN-1392-1.patch, YARN-1392-2.patch,
> YARN-1392.patch
>
>
> Currently the Fair Scheduler supports app-to-queue placement by username. It
> would be beneficial to allow more sophisticated policies that rely on primary
> and secondary groups and fallbacks.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
