Return-Path: 
 <yarn-issues-return-70265-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 9C67618D08
	for <apmail-hadoop-yarn-issues-archive@minotaur.apache.org>;
 Fri, 25 Sep 2015 13:49:04 +0000 (UTC)
Received: (qmail 21459 invoked by uid 500); 25 Sep 2015 13:49:04 -0000
Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org
Received: (qmail 21412 invoked by uid 500); 25 Sep 2015 13:49:04 -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 21400 invoked by uid 99); 25 Sep 2015 13:49:04 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Sep 2015 13:49:04 +0000
Date: Fri, 25 Sep 2015 13:49:04 +0000 (UTC)
From: "apachehadoop (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12762178.1418782316000.72983.1443188944349@Atlassian.JIRA>
In-Reply-To: <JIRA.12762178.1418782316000@Atlassian.JIRA>
References: <JIRA.12762178.1418782316000@Atlassian.JIRA>
 <JIRA.12762178.1418782316776@arcas>
Subject: [jira] [Updated] (YARN-2973) Capacity scheduler configuration ACLs
 not work.
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-2973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

apachehadoop updated YARN-2973:
-------------------------------
    Issue Type: Bug  (was: Improvement)

> Capacity scheduler configuration ACLs not work.
> -----------------------------------------------
>
>                 Key: YARN-2973
>                 URL: https://issues.apache.org/jira/browse/YARN-2973
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: capacityscheduler
>    Affects Versions: 2.5.0
>         Environment: ubuntu 12.04, cloudera manager, cdh5.3.2
>            Reporter: Jimmy Song
>            Assignee: Rohith Sharma K S
>              Labels: acl, capacity-scheduler, yarn
>
> I follow this page to configure yarn: http://archive.cloudera.com/cdh5/cdh/5/hadoop/hadoop-yarn/hadoop-yarn-site/CapacityScheduler.html. 
> I configured YARN to use capacity scheduler in yarn-site.xml with yarn.resourcemanager.scheduler.class for org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler. Then modified capacity-scheduler.xml,
> ___________________________________________________
> <?xml version="1.0"?>
> <configuration>
>   <property>
>     <name>yarn.scheduler.capacity.root.queues</name>
>     <value>default,extract,report,tool</value>
>   </property>
>   <property>
>     <name>yarn.scheduler.capacity.root.state</name>
>     <value>RUNNING</value>
>   </property>
>   <property>
>     <name>yarn.scheduler.capacity.root.default.acl_submit_applications</name>
>     <value>jcsong2, y2 </value>
>   </property>
>   <property>
>     <name>yarn.scheduler.capacity.root.default.acl_administer_queue</name>
>     <value>jcsong2, y2 </value>
>   </property>
>   <property>
>     <name>yarn.scheduler.capacity.root.default.capacity</name>
>     <value>35</value>
>   </property>
>   <property>
>     <name>yarn.scheduler.capacity.root.extract.acl_submit_applications</name>
>     <value>jcsong2 </value>
>   </property>
>   <property>
>     <name>yarn.scheduler.capacity.root.extract.acl_administer_queue</name>
>     <value>jcsong2 </value>
>   </property>
>   <property>
>     <name>yarn.scheduler.capacity.root.extract.capacity</name>
>     <value>15</value>
>   </property>
>   <property>
>     <name>yarn.scheduler.capacity.root.report.acl_submit_applications</name>
>     <value>y2 </value>
>   </property>
>   <property>
>     <name>yarn.scheduler.capacity.root.report.acl_administer_queue</name>
>     <value>y2 </value>
>   </property>
>   <property>
>     <name>yarn.scheduler.capacity.root.report.capacity</name>
>     <value>35</value>
>   </property>
>   <property>
>     <name>yarn.scheduler.capacity.root.tool.acl_submit_applications</name>
>     <value> </value>
>   </property>
>   <property>
>     <name>yarn.scheduler.capacity.root.tool.acl_administer_queue</name>
>     <value> </value>
>   </property>
>   <property>
>     <name>yarn.scheduler.capacity.root.tool.capacity</name>
>     <value>15</value>
>   </property>
> </configuration>
> _______________________________________________
> I have enabled the acl in yarn-site.xml, but the user jcsong2 can submit applications to every queue. The queue acl does't work! And the queue used capacity more than it was configured! 



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