hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sunil G (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-3955) Support for priority ACLs in CapacityScheduler
Date Fri, 06 Jan 2017 04:47:58 GMT

     [ 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.0009.patch

Thanks [~leftnoteasy]

Mostly addressed all comments. 

bq.And in addition, I didn't see test case that parses raw priority acls (string) to List
of PriorityACLGroup. Could you point me if there's any test cases exist?
{{TestApplicationPriorityACLConfiguration}} handles this case.

bq.Not quite sure what did you mean. From my understanding, existing logic read acls from
configs while refreshQueues, and what we need to do is to replace all ACLs instead of append
to previous acl list, correct?
I was planning like below. clear the any queue acl before updating new.
{noformat}
        // Clear Priority ACLs first since reinitialize also call same.
        appPriorityACLManager.clearPriorityACLs(lQueue.getQueueName());
        appPriorityACLManager.addPrioirityACLs(lQueue.getPriorityACLs(),lQueue.getQueueName());
{noformat}
            

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


Mime
View raw message