[
https://issues.apache.org/jira/browse/YARN-5554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15726946#comment-15726946
]
Daniel Templeton commented on YARN-5554:
----------------------------------------
bq. The change to not use the checkAccess() of the scheduler for the capacity
scheduler was made as part of YARN-4571.
I'm looking at YARN-4571, and I can't see any reason why {{checkAccess()}} was
modified to special case the capacity scheduler. The only difference I see
from the code is that the new {{checkAccess()}} plows ahead even if the queue
is null. Maybe there were differences at the time that have since disappeared?
([~jianhe], can you shed any light?)
Looking at your new {{checkAccess()}} method, I also don't see where it does
anything different from the schedulers' {{checkAccess()}} methods. What
problem is it that you're solving with the new method?
> MoveApplicationAcrossQueues does not check user permission on the target queue
> ------------------------------------------------------------------------------
>
> Key: YARN-5554
> URL: https://issues.apache.org/jira/browse/YARN-5554
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Affects Versions: 2.7.2
> Reporter: Haibo Chen
> Assignee: Wilfred Spiegelenburg
> Labels: oct16-medium
> Attachments: YARN-5554.10.patch, YARN-5554.11.patch,
> YARN-5554.2.patch, YARN-5554.3.patch, YARN-5554.4.patch, YARN-5554.5.patch,
> YARN-5554.6.patch, YARN-5554.7.patch, YARN-5554.8.patch, YARN-5554.9.patch
>
>
> moveApplicationAcrossQueues operation currently does not check user
> permission on the target queue. This incorrectly allows one user to move
> his/her own applications to a queue that the user has no access to
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
