Rohith Sharma K S commented on YARN-3250:

Hi [~sunilg]
   As part of this JIRA, 
# User API : 
## I am planning to introduce 
*SetApplicationProrityRequest* comprises of ApplicationId and Priority. The 
clientRMService invokes API introduced by YARN-3887 i.e. 
## Thinking that does getPriority is required at user side?  I feel that, since 
ApplicationReport can gives the priority of an application, this API is NOT 
required to  have. What do you suggests, any thoughts?

# Admin API :
## As admin, he should be able to change the *cluster-max-application-priority* 
value. Having an rmadmin API would be great!!. But one issue in with api is 
that cluster-max-application-priority is inmemory, but when rmadmin updates it, 
inmemory value can be updated. But in HA/Restart cases, the  configuration 
value is taken. So I suggest to store cluster-level-application-priority in 
store and whenever RM is switched/Restarted, give higher preference to store. 
What do you think about this approach? 

Apart from above API's , should there any new API's to be added? Kindly 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

Reply via email to