Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 6623F200C17 for ; Thu, 5 Jan 2017 20:21:00 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 64C82160B26; Thu, 5 Jan 2017 19:21:00 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id B0CBF160B45 for ; Thu, 5 Jan 2017 20:20:59 +0100 (CET) Received: (qmail 12704 invoked by uid 500); 5 Jan 2017 19:20:58 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 12363 invoked by uid 99); 5 Jan 2017 19:20:58 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Jan 2017 19:20:58 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id AEFD82C2AC2 for ; Thu, 5 Jan 2017 19:20:58 +0000 (UTC) Date: Thu, 5 Jan 2017 19:20:58 +0000 (UTC) From: "Wangda Tan (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-5556) Support for deleting queues without requiring a RM restart MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 05 Jan 2017 19:21:00 -0000 [ https://issues.apache.org/jira/browse/YARN-5556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15802255#comment-15802255 ] Wangda Tan commented on YARN-5556: ---------------------------------- Just offline discussed with [~xgong]. I think we don't need the additional DELETED state, first it generate some maintenance overheads, for example we need to maintain state transition to/from of the DELETED state. And since by design a queue can be deleted only if queue is stopped and no app running, so the impact of typo should be minimum. Our preference is simply remove queue from config. And for re-distribution of stopped/deleted queue. For delete queue it should be obvious, since the queue is gone, sum of its siblings should be 100. For stopped queue, our expectation is, it will be reactivated at some time. So it will be better to keep the capacity as-is, and admin can update max-capacity of its siblings to make sure queue capacity can be utilized. I think we need to update design doc to make it up-to-date. Thoughts? > Support for deleting queues without requiring a RM restart > ---------------------------------------------------------- > > Key: YARN-5556 > URL: https://issues.apache.org/jira/browse/YARN-5556 > Project: Hadoop YARN > Issue Type: Sub-task > Components: yarn > Reporter: Xuan Gong > Assignee: Naganarasimha G R > Attachments: YARN-5556.v1.001.patch, YARN-5556.v1.002.patch, YARN-5556.v1.003.patch, YARN-5556.v1.004.patch > > > Today, we could add or modify queues without restarting the RM, via a CS refresh. But for deleting queue, we have to restart the ResourceManager. We could support for deleting queues without requiring a RM restart -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org