Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EC5E2EC54 for ; Thu, 31 Jan 2013 03:23:15 +0000 (UTC) Received: (qmail 99871 invoked by uid 500); 31 Jan 2013 03:23:15 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 99834 invoked by uid 500); 31 Jan 2013 03:23:15 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 99794 invoked by uid 99); 31 Jan 2013 03:23:14 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 31 Jan 2013 03:23:14 +0000 Date: Thu, 31 Jan 2013 03:23:14 +0000 (UTC) From: "Sandy Ryza (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-333) Schedulers cannot control the queue-name of an application MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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