[
https://issues.apache.org/jira/browse/YARN-899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13731729#comment-13731729
]
Sandy Ryza commented on YARN-899:
---------------------------------
Thanks for taking this up, Xuan. I took a look at the patch. It appears to
put Capacity Scheduler-specific code in the RM outside the Capacity Scheduler.
The added QueueACLsManager, which is referenced in many places in the RM, holds
a mapping between application IDs and CSQueues. We should go with an approach
that generalizes for all schedulers.
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.
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.
> 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
