Hi Rohith Sharma K S
Thank you for bringing up with api suggestions. I have few comments.
Could we use api name as setApplicationPriority
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.
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.
./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/Jian He Wangda Tan Please share your thoughts.