Return-Path: 
 <yarn-issues-return-12611-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 B6BF210AAC
	for <apmail-hadoop-yarn-issues-archive@minotaur.apache.org>;
 Wed,  7 Aug 2013 16:44:55 +0000 (UTC)
Received: (qmail 66792 invoked by uid 500); 7 Aug 2013 16:44:51 -0000
Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org
Received: (qmail 66632 invoked by uid 500); 7 Aug 2013 16:44:51 -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 66602 invoked by uid 99); 7 Aug 2013 16:44:50 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Aug 2013 16:44:50 +0000
Date: Wed, 7 Aug 2013 16:44:50 +0000 (UTC)
From: "Xuan Gong (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12656115.1372885987217.17059.1375893890842@arcas>
In-Reply-To: <JIRA.12656115.1372885987217@arcas>
References: <JIRA.12656115.1372885987217@arcas>
Subject: [jira] [Commented] (YARN-899) Get queue administration ACLs working
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-899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13732148#comment-13732148 ] 

Xuan Gong commented on YARN-899:
--------------------------------

Thanks for the comments. Sandy.

bq.We should go with an approach that generalizes for all schedulers.

Yes, we should do that. How about using a more generalized type : Queue. Looks like that Queue is the super type for all the csqueue, FSQueue, and queue used in all three schedulers.

bq.Queue submission ACLs are enforced internally by the schedulers on addApplication. Would it make sense to use a similar approach with removeApplication? If not, the submission ACLs should probably be modified to use whatever mechanism is added.

We can do that

bq.In MR1, did the administer ACLs control who could view jobs in a queue? My impression was that they only controlled who could kill jobs and change their priorities.

Yes, based on the documentation, it shows "queue administrators of the queue to which the job was submitted to (mapred.queue.queue-name.acl-administer-jobs) always have access to view and modify a job ". 




                
> Get queue administration ACLs working
> -------------------------------------
>
>                 Key: YARN-899
>                 URL: https://issues.apache.org/jira/browse/YARN-899
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: scheduler
>    Affects Versions: 2.1.0-beta
>            Reporter: Sandy Ryza
>            Assignee: Xuan Gong
>         Attachments: YARN-899.1.patch
>
>
> The Capacity Scheduler documents the yarn.scheduler.capacity.root.<queue-path>.acl_administer_queue config option for controlling who can administer a queue, but it is not hooked up to anything.  The Fair Scheduler could make use of a similar option as well.  This is a feature-parity regression from MR1.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira