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

Sunil G commented on YARN-2693:
-------------------------------

Thank you [~wangda] for sharing comments.

As we move in the queue specific config inside scheduler.Queue, are we also 
taking ACLs back to scheduler (ACL wrt priority). Its better to control ACL 
from outside YarnAuthorizer and config only can be kept w.r.t scheduler. Pls 
share your thoughts.
 
Regarding methods in ApplicationPrioirtyManager, it looks overall fine but I 
suggest we may need 
* getClusterApplicationPriorities (if its range, that can be sent back)


> Priority Label Manager in RM to manage application priority based on 
> configuration
> ----------------------------------------------------------------------------------
>
>                 Key: YARN-2693
>                 URL: https://issues.apache.org/jira/browse/YARN-2693
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Sunil G
>            Assignee: Sunil G
>         Attachments: 0001-YARN-2693.patch, 0002-YARN-2693.patch, 
> 0003-YARN-2693.patch, 0004-YARN-2693.patch, 0005-YARN-2693.patch, 
> 0006-YARN-2693.patch
>
>
> Focus of this JIRA is to have a centralized service to handle priority labels.
> Support operations such as
> * Add/Delete priority label to a specified queue
> * Manage integer mapping associated with each priority label
> * Support managing default priority label of a given queue
> * Expose interface to RM to validate priority label
> TO have simplified interface, Priority Manager will support only 
> configuration file in contrast with admin cli and REST. 



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

Reply via email to