[
https://issues.apache.org/jira/browse/YARN-899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13734164#comment-13734164
]
Xuan Gong commented on YARN-899:
--------------------------------
Here is my propose:
We can create QueueACLsManager which encapsulate the ResourceScheduler, so
whenever we need to check user's permission, we can provide the UGI,
queueName(This can be found from RMApp) to the Scheduler (No matter it is
CapacityScheduler, fairScheduler or FIFOScheduler), and let scheduler to help
us make the decision.
For each scheduler, we may need to add a new interface :
Scheduler#hasAccess(UGI, queueName). The queueName is used to find the correct
Queue. The reason why I send information back to Scheduler and let scheduler
make the decision is because
a. I think all the QueueACLsInfos are collected by the Scheduler, and save in
its queues (I can not find other places which save the QueueACLs),
b. even if the queue is re-initiated in the future, we do not need to worry
about it.
Attached is the patch implements this propose. Please give me the suggestions.
> 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, YARN-899.2.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
