[ 
https://issues.apache.org/jira/browse/YARN-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14205445#comment-14205445
 ] 

Eric Payne commented on YARN-1963:
----------------------------------

Thanks a lot [~sunilg] for taking the lead on this and putting together the 
design document. I have a question about per-priority ACLs.

Can per-priority ACLs within a queue be inherited from queue-level ACLs if the 
per-priority ACLs aren't there? In a cluster that already has queues divided to 
be specific to business units, they will want to only specify the queue-level 
ACL list. In other words, in this use case, the queue-level users are already 
trusted enough to modify apps on that queue, regardless of priority, so they 
won't want the extra overhead of specifying additional priority-level ACLs. Is 
that part of the design?

> Support priorities across applications within the same queue 
> -------------------------------------------------------------
>
>                 Key: YARN-1963
>                 URL: https://issues.apache.org/jira/browse/YARN-1963
>             Project: Hadoop YARN
>          Issue Type: New Feature
>          Components: api, resourcemanager
>            Reporter: Arun C Murthy
>            Assignee: Sunil G
>         Attachments: YARN Application Priorities Design.pdf
>
>
> It will be very useful to support priorities among applications within the 
> same queue, particularly in production scenarios. It allows for finer-grained 
> controls without having to force admins to create a multitude of queues, plus 
> allows existing applications to continue using existing queues which are 
> usually part of institutional memory.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to