[
https://issues.apache.org/jira/browse/YARN-2575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15102876#comment-15102876
]
Subru Krishnan commented on YARN-2575:
--------------------------------------
[~seanpo03], ReservationACLs does not ignore hierarchies as reservations are
currently only supported on leaf queues. I hope that clarifies my suggestion.
We should only look for ReservationACLs in the leaf queue in the Scheduler to
keep it simple.
Additionally we need to ensure an admin user can list/update/delete
reservations. Unit test validating the same will be great.
> Consider creating separate ACLs for Reservation create/update/delete/list ops
> -----------------------------------------------------------------------------
>
> Key: YARN-2575
> URL: https://issues.apache.org/jira/browse/YARN-2575
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: capacityscheduler, fairscheduler, resourcemanager
> Reporter: Subru Krishnan
> Assignee: Sean Po
> Attachments: YARN-2575.v1.patch, YARN-2575.v2.1.patch,
> YARN-2575.v2.patch, YARN-2575.v3.patch, YARN-2575.v4.patch
>
>
> YARN-1051 introduces the ReservationSystem and in the current implementation
> anyone who can submit applications can also submit reservations. This JIRA is
> to evaluate creating separate ACLs for Reservation create/update/delete ops.
> Depends on YARN-4340
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
