You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Subru Krishnan (JIRA)" <ji...@apache.org> on 2016/01/04 22:09:39 UTC
[jira] [Commented] (YARN-2575) Consider creating separate ACLs for
Reservation create/update/delete/list ops
[ https://issues.apache.org/jira/browse/YARN-2575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15081807#comment-15081807 ]
Subru Krishnan commented on YARN-2575:
--------------------------------------
I am wondering whether we have covered the behavior for the following 2 scenarios:
* When Reservation ACLs are not enabled - in this case, everyone should have access.
* When Reservation ACLs are enabled but not defined - in this case also I think everyone should have access. [~asuresh], can you confirm?
> 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)