[ 
https://issues.apache.org/jira/browse/YARN-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Lowe resolved YARN-1966.
------------------------------

    Resolution: Duplicate

This is a duplicate of YARN-1269 and related to YARN-1941 and YARN-1951.

In any case I don't think we want to special-case the root queue, as the same 
issue could exist in a subtree where access to the subtree root allows access 
to any queue within the subtree.

Actually I believe this is by design.  It allows admins to configure access to 
an entire subtree of queues by giving access to the root of the subtree rather 
than having to add the access to each leaf queue.  So for your example above 
you'll want to set the root queue's ACLs to be empty so that one must have 
access to the leaf queue in order to submit.

> Capacity Scheduler acl_submit_applications in Leaf Queue finally considers 
> root queue default always
> ----------------------------------------------------------------------------------------------------
>
>                 Key: YARN-1966
>                 URL: https://issues.apache.org/jira/browse/YARN-1966
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.4.0
>            Reporter: Sunil G
>         Attachments: Yarn-1966.1.patch
>
>
> Given with below configurations,
> <property>
>   <name>yarn.scheduler.capacity.root.queues</name>
>   <value>fast,medium</value>
> </property>
> <property>
>   <name>yarn.scheduler.capacity.root.fast.acl_submit_applications</name>
>   <value>hadoop</value>
> </property>
> <property>
>   <name>yarn.scheduler.capacity.root.slow.acl_submit_applications</name>
>   <value>hadoop</value>
> </property>
> In this case, the expectation is like "hadoop" user can only submit job to 
> "fast" or "slow" queue.
> But now any user can submit job to these queues.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to