[ https://issues.apache.org/jira/browse/YARN-2575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Po updated YARN-2575: -------------------------- Attachment: YARN-2575.v4.patch Thanks Subru, I addressed your comments in this latest patch. The one comment I wasn't sure about was: "We should return the default ACLs, i.e. everyone has access in ReservationSchedulerConfiguration::getReservationAcls" Do you mean that we should make it so that if no users are given in the conf, that we should allow everyone to have access? > 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)