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 C6D0511397 for ; Mon, 21 Apr 2014 11:43:17 +0000 (UTC) Received: (qmail 34312 invoked by uid 500); 21 Apr 2014 11:43:16 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 34285 invoked by uid 500); 21 Apr 2014 11:43: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 34276 invoked by uid 99); 21 Apr 2014 11:43:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Apr 2014 11:43:15 +0000 Date: Mon, 21 Apr 2014 11:43:14 +0000 (UTC) From: "Sunil G (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (YARN-1966) Capacity Scheduler acl_submit_applications in Leaf Queue finally considers root queue default always 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-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-1966: -------------------------- Attachment: Yarn-1966.1.patch Here issue is happening because while submitting an application, hasAccess() check will always reach ParentQueue::hasAccess(). In this case, finally parent will come as "root" and it will pass this check. (* is default for acl_submit_applications and acl_administer_queue in root queue) So to ensure only one specified user to submit job in a leaf queue, below configurations are mandatory in "root" root.acl_submit_applications root.acl_administer_queue To submit a job, acl_administer_queue check has no relevance. But we are forced to configure this also, if we want to achieve what is mentioned in the problem statement of this issue. Also if each leaf queue wants to have its own set of users, all users finally are to be mentioned in root. This is not good. So it is better to skip hasAccess() check if parent Queue is "root" as below if(rootQueue){ return false; } > Capacity Scheduler acl_submit_applications in Leaf Queue finally considers root queue default always > ---------------------------------------------------------------------------------------------------- > > Key: YARN-1966 > URL: https://issues.apache.org/jira/browse/YARN-1966 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager > Affects Versions: 2.4.0 > Reporter: Sunil G > Attachments: Yarn-1966.1.patch > > > Given with below configurations, > > yarn.scheduler.capacity.root.queues > fast,medium > > > yarn.scheduler.capacity.root.fast.acl_submit_applications > hadoop > > > yarn.scheduler.capacity.root.slow.acl_submit_applications > hadoop > > In this case, the expectation is like "hadoop" user can only submit job to "fast" or "slow" queue. > But now any user can submit job to these queues. -- This message was sent by Atlassian JIRA (v6.2#6252)