From yarn-issues-return-155435-apmail-hadoop-yarn-issues-archive=hadoop.apache.org@hadoop.apache.org Tue Oct 16 18:22:04 2018 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 A434B19D5F for ; Tue, 16 Oct 2018 18:22:04 +0000 (UTC) Received: (qmail 7391 invoked by uid 500); 16 Oct 2018 18:22:04 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 7339 invoked by uid 500); 16 Oct 2018 18:22:04 -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 7328 invoked by uid 99); 16 Oct 2018 18:22:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Oct 2018 18:22:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 9D33718214A for ; Tue, 16 Oct 2018 18:22:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.301 X-Spam-Level: X-Spam-Status: No, score=-110.301 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id ZEnirC5g6-tm for ; Tue, 16 Oct 2018 18:22:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 0986260D2B for ; Tue, 16 Oct 2018 18:22:02 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 41250E0E5D for ; Tue, 16 Oct 2018 18:22:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 4D5DD24DF8 for ; Tue, 16 Oct 2018 18:22:00 +0000 (UTC) Date: Tue, 16 Oct 2018 18:22:00 +0000 (UTC) From: "Eric Payne (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-8647) Add a flag to disable move app between queues MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-8647?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16652= 189#comment-16652189 ]=20 Eric Payne commented on YARN-8647: ---------------------------------- {quote}{quote}Addition flag to disable required {quote} {quote}IMO we shouldn't require another flag to disable it as we are alread= y checking for all the permissions. {quote} we want to disable the feature of move queue on cluster level instead of di= sabling for few users {quote} [~saruntek], I understand that it would be easier for an admin to just set = the flag and forget it. However, I would argue that if a multi-tenant clust= er has hundreds of users, it's time to manage the usage more closely by uti= lizing ACL permissions on each queue. In general, I would prefer to not add= code to the scheduler when there is already a pre-designed alternative. > Add a flag to disable move app between queues > --------------------------------------------- > > Key: YARN-8647 > URL: https://issues.apache.org/jira/browse/YARN-8647 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager > Affects Versions: 2.7.3 > Reporter: sarun singla > Assignee: Abhishek Modi > Priority: Critical > > For large clusters where we have a number of users submitting application= , we can result into scenarios where app developers try to move the queues = for their applications using something like=C2=A0 > {code:java} > yarn application -movetoqueue -queue {code} > Today there is no way of disabling the feature if one does not want appli= cation developers to use=C2=A0 the feature. > *Solution:* > We should probably add an option to disable move queue feature from RM si= de on the cluster level. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org