Return-Path: 
 <yarn-issues-return-74450-apmail-hadoop-yarn-issues-archive=hadoop.apache.org@hadoop.apache.org>
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 965E81862D
	for <apmail-hadoop-yarn-issues-archive@minotaur.apache.org>;
 Tue,  1 Dec 2015 02:47:16 +0000 (UTC)
Received: (qmail 95825 invoked by uid 500); 1 Dec 2015 02:47:11 -0000
Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org
Received: (qmail 95743 invoked by uid 500); 1 Dec 2015 02:47:11 -0000
Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:yarn-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:yarn-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:yarn-issues@hadoop.apache.org>
List-Id: <yarn-issues.hadoop.apache.org>
Reply-To: yarn-issues@hadoop.apache.org
Delivered-To: mailing list yarn-issues@hadoop.apache.org
Received: (qmail 95691 invoked by uid 99); 1 Dec 2015 02:47:11 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Dec 2015 02:47:11 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id 05C412C1F72
	for <yarn-issues@hadoop.apache.org>; Tue,  1 Dec 2015 02:47:11 +0000 (UTC)
Date: Tue, 1 Dec 2015 02:47:11 +0000 (UTC)
From: "stefanlee (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12852529.1438854689000.227557.1448938031020@Atlassian.JIRA>
In-Reply-To: <JIRA.12852529.1438854689000@Atlassian.JIRA>
References: <JIRA.12852529.1438854689000@Atlassian.JIRA>
 <JIRA.12852529.1438854689771@arcas>
Subject: [jira] [Commented] (YARN-4022) queue not remove from
 webpage(/cluster/scheduler) when delete queue in xxx-scheduler.xml
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-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15032978#comment-15032978 ] 

stefanlee commented on YARN-4022:
---------------------------------

hi forrestchen, my configuration in cluster is similar to you  ,and when i delete a queue in fair-scheduler.xml,I submit an application to the deleted queue and the application will run using 'root.default' queue instead, then  submit to an un-exist queue ,but still run using 'root.default' and no exception. why ? my hadoop version is 2.4.0

> queue not remove from webpage(/cluster/scheduler) when delete queue in xxx-scheduler.xml
> ----------------------------------------------------------------------------------------
>
>                 Key: YARN-4022
>                 URL: https://issues.apache.org/jira/browse/YARN-4022
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.7.1
>            Reporter: forrestchen
>              Labels: scheduler
>         Attachments: YARN-4022.001.patch, YARN-4022.002.patch, YARN-4022.003.patch, YARN-4022.004.patch
>
>
> When I delete an existing queue by modify the xxx-schedule.xml, I can still see the queue information block in webpage(/cluster/scheduler) though the 'Min Resources' items all become to zero and have no item of 'Max Running Applications'.
> I can still submit an application to the deleted queue and the application will run using 'root.default' queue instead, but submit to an un-exist queue will cause an exception.
> My expectation is the deleted queue will not displayed in webpage and submit application to the deleted queue will act just like the queue doesn't exist.
> PS: There's no application running in the queue I delete.
> Some related config in yarn-site.xml:
> {code}
> <property>
>         <name>yarn.scheduler.fair.user-as-default-queue</name>
>         <value>false</value>
> </property>
> <property>
>         <name>yarn.scheduler.fair.allow-undeclared-pools</name>
>         <value>false</value>
> </property>
> {code}
> a related question is here: http://stackoverflow.com/questions/26488564/hadoop-yarn-why-the-queue-cannot-be-deleted-after-i-revise-my-fair-scheduler-xm



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)