[
https://issues.apache.org/jira/browse/YARN-899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13732576#comment-13732576
]
Hitesh Shah commented on YARN-899:
----------------------------------
[~acmurthy] [~vinodkv] can probably correct me as I will likely make some
mistakes.
>From what I know, acls can control both view and modification abilities. There
>are separate acls for who can view as compared to who can modify ( kill, etc ).
In case of YARN, a queue is a YARN construct. Queue acls should be enforced by
YARN and not by each scheduler. I know that this is a problem as queue
configuration is scheduler specific but we need to look at providing a global
solution to acls and see how that works with the configured queues in
themselves. YARN already has cluster level acls for applications. Queue acls
would be a layer above it but should be available and enforcable regardless of
what scheduler is used.
> 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
