[jira] [Commented] (YARN-333) Schedulers cannot control the queue-name of an application
[ https://issues.apache.org/jira/browse/YARN-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13706849#comment-13706849 ] Hudson commented on YARN-333: - SUCCESS: Integrated in Hadoop-Yarn-trunk #268 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/268/]) YARN-333. Schedulers cannot control the queue-name of an application. (sandyr via tucu) (tucu: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1502374) * /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmapp/RMApp.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmapp/RMAppImpl.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/FairScheduler.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/applicationsmanager/MockAsm.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/TestFairScheduler.java Schedulers cannot control the queue-name of an application -- 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 Fix For: 2.1.0-beta Attachments: YARN-333-1.patch, YARN-333-2.patch, YARN-333-3.patch, 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
[jira] [Commented] (YARN-333) Schedulers cannot control the queue-name of an application
[ https://issues.apache.org/jira/browse/YARN-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13706918#comment-13706918 ] Hudson commented on YARN-333: - FAILURE: Integrated in Hadoop-Hdfs-trunk #1458 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1458/]) YARN-333. Schedulers cannot control the queue-name of an application. (sandyr via tucu) (tucu: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1502374) * /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmapp/RMApp.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmapp/RMAppImpl.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/FairScheduler.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/applicationsmanager/MockAsm.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/TestFairScheduler.java Schedulers cannot control the queue-name of an application -- 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 Fix For: 2.1.0-beta Attachments: YARN-333-1.patch, YARN-333-2.patch, YARN-333-3.patch, 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
[jira] [Commented] (YARN-333) Schedulers cannot control the queue-name of an application
[ https://issues.apache.org/jira/browse/YARN-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13706955#comment-13706955 ] Hudson commented on YARN-333: - SUCCESS: Integrated in Hadoop-Mapreduce-trunk #1485 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1485/]) YARN-333. Schedulers cannot control the queue-name of an application. (sandyr via tucu) (tucu: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1502374) * /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmapp/RMApp.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmapp/RMAppImpl.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/FairScheduler.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/applicationsmanager/MockAsm.java * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/TestFairScheduler.java Schedulers cannot control the queue-name of an application -- 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 Fix For: 2.1.0-beta Attachments: YARN-333-1.patch, YARN-333-2.patch, YARN-333-3.patch, 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
[jira] [Commented] (YARN-333) Schedulers cannot control the queue-name of an application
[ https://issues.apache.org/jira/browse/YARN-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13706271#comment-13706271 ] Sandy Ryza commented on YARN-333: - Attached rebased patch. Schedulers cannot control the queue-name of an application -- 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-1.patch, YARN-333-2.patch, YARN-333-3.patch, 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
[jira] [Commented] (YARN-333) Schedulers cannot control the queue-name of an application
[ https://issues.apache.org/jira/browse/YARN-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682909#comment-13682909 ] Sandy Ryza commented on YARN-333: - Uploading a patch that adds a setQueue method to RMApp, allowing a scheduler to change the name of an application. RMApp was previously read-only, so this is a departure from that, but I couldn't think of a case where changing a queue name would cause a problem. We could use an event here, but it seems like overkill to me when we're just setting a single field. Schedulers cannot control the queue-name of an application -- 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
[jira] [Commented] (YARN-333) Schedulers cannot control the queue-name of an application
[ https://issues.apache.org/jira/browse/YARN-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682916#comment-13682916 ] Alejandro Abdelnur commented on YARN-333: - The approach on the latest patch is much simpler than previously discussed. As the RMApp.getQueue() is not used as a key in any data structure in the ResourceManager side (only used for reporting), it is safe to make it settable. Having a testcase that verifies this does the trick for the FS would be great. Schedulers cannot control the queue-name of an application -- 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-1.patch, 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
[jira] [Commented] (YARN-333) Schedulers cannot control the queue-name of an application
[
https://issues.apache.org/jira/browse/YARN-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682932#comment-13682932
]
Hadoop QA commented on YARN-333:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12587732/YARN-333-1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 javadoc{color}. The javadoc tool appears to have generated 1
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/1229//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/1229//console
This message is automatically generated.
Schedulers cannot control the queue-name of an application
--
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-1.patch, 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
[jira] [Commented] (YARN-333) Schedulers cannot control the queue-name of an application
[ https://issues.apache.org/jira/browse/YARN-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682958#comment-13682958 ] Sandy Ryza commented on YARN-333: - Attached an updated patch that includes a test Schedulers cannot control the queue-name of an application -- 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-1.patch, YARN-333-2.patch, 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
[jira] [Commented] (YARN-333) Schedulers cannot control the queue-name of an application
[
https://issues.apache.org/jira/browse/YARN-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13683027#comment-13683027
]
Hadoop QA commented on YARN-333:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12587744/YARN-333-2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/1235//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/1235//console
This message is automatically generated.
Schedulers cannot control the queue-name of an application
--
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-1.patch, YARN-333-2.patch, 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
[jira] [Commented] (YARN-333) Schedulers cannot control the queue-name of an application
[ https://issues.apache.org/jira/browse/YARN-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13683032#comment-13683032 ] Alejandro Abdelnur commented on YARN-333: - +1, LGTM. Schedulers cannot control the queue-name of an application -- 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-1.patch, YARN-333-2.patch, 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
[jira] [Commented] (YARN-333) Schedulers cannot control the queue-name of an application
[ https://issues.apache.org/jira/browse/YARN-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13635606#comment-13635606 ] Alejandro Abdelnur commented on YARN-333: - Stepping back a bit. In Hadoop 1, using fair-scheduler, the following is possible: *1 On job submission, the scheduler resolves/reassigns the queue of the job. For example, your jobconf states 'default' as queue, and the fair-scheduler converts the queue to the user primary group *2 For a running job, via the fair-scheduler UI, it is possible to change the queue of the job (enforcing queue ACLs) While there are a few minor quirks (the JobInProgress does not get update to the right queeu), this works fine and you can see the new queue in most of the UI (scheduler owns most of the UI that shows queues). In Hadoop 2, using fair-scheduler: *1, this is still doable but all the feedback to the user is provided by the RM which does not know about the queue name change. Thus there is a split-brain perception and it can lead to wrong decisions by admin trying to troubleshoot cluster utilization *2, this is not currently possible I see 2 ways to go about: *A make the necessary changes for the fair-scheduler to be able to provide #1 and #2 as a fair-scheduler only solution *B make the necessary changes so all schedulers support this capability To do #A, the fair-scheduler should be able, via the RMContext, change the queue of job in the RM. This would take care of #1 and #2. Still it is the responsibility of the fair-scheduler to provide an end-point to the user/admin to perfom #2. To do #B, the ClientRMProtocol would have a new 'changeQueue(String queueName)' method, the YarnScheduler would have a new 'String getActualQueue(String queueName)' method. On job submission the RM would call the scheduler 'getActualQueue()' method to resolve the actual queue for the job (this takes care of #1). On a 'changeQueue()' call, the RM also calls the scheduler 'getActualQueue()'. Note that on both approaches, the scheduler is still responsible for enforcing queue ACLs as it is done today. The benefit I see in #B, is that will be consistent for the different scheduler implementations. It will also leverage the existing client RPC, so no need to worry about a different endpoint and the security considerations this means. Schedulers cannot control the queue-name of an application -- 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
[jira] [Commented] (YARN-333) Schedulers cannot control the queue-name of an application
[ https://issues.apache.org/jira/browse/YARN-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13635837#comment-13635837 ] Alejandro Abdelnur commented on YARN-333: - In case is not clear, I favor #B Schedulers cannot control the queue-name of an application -- 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
[jira] [Commented] (YARN-333) Schedulers cannot control the queue-name of an application
[ https://issues.apache.org/jira/browse/YARN-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13567305#comment-13567305 ] Sandy Ryza commented on YARN-333: - Thanks, agreed that that's a better title. Schedulers cannot control the queue-name of an application -- 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
[jira] [Commented] (YARN-333) Schedulers cannot control the queue-name of an application
[ https://issues.apache.org/jira/browse/YARN-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13567313#comment-13567313 ] Sandy Ryza commented on YARN-333: - Just realized I was thinking of ApplicationSubmissionContext - so I think my last comment isn't entirely relevant. I couldn't find ApplicationSchedulingContext anywhere in the code - are saying that it would be a handle that would allow the scheduler to make changes later on? Schedulers cannot control the queue-name of an application -- 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
