[
https://issues.apache.org/jira/browse/YARN-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandy Ryza updated YARN-333:
----------------------------
Description:
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.
was:
When the fair scheduler user-as-default-queue config option is set to true, and
a job is submitted with no queue specified, the fair scheduler assigns the job
to a queue with the user's name. The RM, on the other hand, sets the
corresponding RMApp's queue to be "default".
This causes mapred queue -info -showJobs to work incorrectly.
Because the RMApp is instantiated first, fixing this probably requires adding
in the ability to change an RMApp's queue.
> 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
>
> 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
