[
https://issues.apache.org/jira/browse/YARN-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567303#comment-13567303
]
Vinod Kumar Vavilapalli commented on YARN-333:
----------------------------------------------
I think instead of adding it to YarnScheduler (which will force us to think
more carefully about synchronization etc), it is better to change
{{AppAddedSchedulerEvent}} to pass {{ApplicationSchedulingContext}} and let
schedulers override the queue name at that time. That way we will also be
future proof of any more information needed by schedulers regarding an app.
Also, passing the app scheduling context will let some exotic futuristic
scheduler to move apps across queues at runtime :)
> On app submission, have RM ask scheduler for queue name
> -------------------------------------------------------
>
> Key: YARN-333
> URL: https://issues.apache.org/jira/browse/YARN-333
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.0.2-alpha
> Reporter: Sandy Ryza
> Assignee: Sandy Ryza
> Attachments: YARN-333.patch
>
>
> Currently, if an app is submitted without a queue, RMAppManager sets the
> RMApp's queue to "default".
> A scheduler may wish to make its own decision on which queue to place an app
> in if none is specified. For example, when the fair scheduler
> user-as-default-queue config option is set to true, and an app is submitted
> with no queue specified, the fair scheduler should assign the app to a queue
> with the user's name.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
