[ 
https://issues.apache.org/jira/browse/YARN-3955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15755127#comment-15755127
 ] 

Sunil G commented on YARN-3955:
-------------------------------

HI [~leftnoteasy]

Thanks for the comments. I will work on tests/findbugs/ and comments.

In general I have one doubt below point.
bq.Instead of call methods of appPriorityAclManager (I prefer to remove it, see 
#1). Can we call scheduler#checkAndGetApplicationPriority to achieve the same 
goal?

I think with {{QueueACLsManager}}, we took ACLs out of CS and managed 
externally. Yes, it was to plugin external ACLs policies, however I thought it 
was good. I think that was the reason I went with a PriorityACLManager model. 
Do you see adding PrioirtyACLs back to scheduler is better? If so, as suggested 
we can leverage from scheduler apis. Thoughts?

> 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.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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to