Return-Path: <yarn-issues-return-105282-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org>
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 73FA6200BF4
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Fri,  6 Jan 2017 08:38:01 +0100 (CET)
Received: by cust-asf.ponee.io (Postfix)
	id 7290A160B37; Fri,  6 Jan 2017 07:38:01 +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 C0167160B1F
	for <archive-asf-public@cust-asf.ponee.io>; Fri,  6 Jan 2017 08:38:00 +0100 (CET)
Received: (qmail 14869 invoked by uid 500); 6 Jan 2017 07:37:59 -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>
Delivered-To: mailing list yarn-issues@hadoop.apache.org
Received: (qmail 14186 invoked by uid 99); 6 Jan 2017 07:37:59 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Jan 2017 07:37:59 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id 21EF22C2A6A
	for <yarn-issues@hadoop.apache.org>; Fri,  6 Jan 2017 07:37:59 +0000 (UTC)
Date: Fri, 6 Jan 2017 07:37:59 +0000 (UTC)
From: "Sunil G (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12846911.1437576254000.662359.1483688279135@Atlassian.JIRA>
In-Reply-To: <JIRA.12846911.1437576254000@Atlassian.JIRA>
References: <JIRA.12846911.1437576254000@Atlassian.JIRA> <JIRA.12846911.1437576254102@arcas>
Subject: [jira] [Updated] (YARN-3955) Support for priority ACLs in
 CapacityScheduler
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
archived-at: Fri, 06 Jan 2017 07:38:01 -0000


     [ https://issues.apache.org/jira/browse/YARN-3955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sunil G updated YARN-3955:
--------------------------
    Attachment: YARN-3955.0010.patch

Thanks [~leftnoteasy] for pointing out. Missed it.

Attaching a new patch addressing the same.

> Support for priority ACLs in CapacityScheduler
> ----------------------------------------------
>
>                 Key: YARN-3955
>                 URL: https://issues.apache.org/jira/browse/YARN-3955
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: capacityscheduler
>            Reporter: Sunil G
>            Assignee: Sunil G
>         Attachments: ApplicationPriority-ACL.pdf, ApplicationPriority-ACLs-v2.pdf, YARN-3955.0001.patch, YARN-3955.0002.patch, YARN-3955.0003.patch, YARN-3955.0004.patch, YARN-3955.0005.patch, YARN-3955.0006.patch, YARN-3955.0007.patch, YARN-3955.0008.patch, YARN-3955.0009.patch, YARN-3955.0010.patch, YARN-3955.v0.patch, YARN-3955.v1.patch, YARN-3955.wip1.patch
>
>
> Support will be added for User-level access permission to use different application-priorities. This is to avoid situations where all users try running max priority in the cluster and thus degrading the value of priorities.
> Access Control Lists can be set per priority level within each queue. Below is an example configuration that can be added in capacity scheduler configuration
> file for each Queue level.
> yarn.scheduler.capacity.root.<queue_name>.<priority>.acl=user1,user2



--
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