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

Sunil G commented on YARN-3250:
-------------------------------

Hi [~rohithsharma]
Thank you for bringing up  with api suggestions. I have few comments.

bq.ApplicationClientProtocol#setPriority(SetApplicationProrityRequest)
Could we use api name as {{setApplicationPriority}}

bq. I suggest to store cluster-level-application-priority in store and whenever 
RM is switched/Restarted, give higher preference to store.
I think this is a known design dilema we have in Yarn now. Once a centralized 
config tickets are done, we can have a clear solution. I am fine with having a 
priority given to RMStateStore over config file during restart. If there are no 
configuration changes, we can use value from yarn-site.xml. How will be the 
storage location path for this cluster-application-priority. I think we can 
group under cluster level so in future common other cluster configs can be 
placed if needed.

bq.Apart from above API's , should there any new API's to be added? 
We can change default priority of a queue by changing capacity-scheduler.xml 
and call refreshQueues. I feel we may not need a command for that now.


bq../yarn application -set-priority <ApplicationId> --priority <value>
I feel we can have {{./yarn application --setPriority <ApplicationId> 
--priority <value>}}
I was trying to sync with existing application commands {{-appStates}} 
{{-appTypes}}

cc/[~jianhe] [~leftnoteasy] Please share your thoughts.

> Support admin/user cli interface in for Application Priority
> ------------------------------------------------------------
>
>                 Key: YARN-3250
>                 URL: https://issues.apache.org/jira/browse/YARN-3250
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Sunil G
>            Assignee: Rohith Sharma K S
>
> Current Application Priority Manager supports only configuration via file. 
> To support runtime configurations for admin cli and REST, a common management 
> interface has to be added which can be shared with NodeLabelsManager. 



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

Reply via email to