[
https://issues.apache.org/jira/browse/YARN-5865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sunil G updated YARN-5865:
--------------------------
Attachment: YARN-5865.0002.patch
Thanks [~jianhe] and [~rohithsharma] for the comments.
Generally makes sense as priority update was depending on submission context.
I made few changes now.
- submission context will still be used to store priority. But this will not be
used as a working data in scheduler any more
- new priority variable will be kept in RMAppImpl. This will be the in-memory
storage for priority for app
- all getters from REST/api's etc will be using
{{RMApp#getApplicationPriority}} instead of the submission context api.
Also we ensure that any edit to submission context will be done only to track
HA scenarios and it will be under write lock of app id.
> Retrospect updateApplicationPriority api to handle state store exception in
> align with YARN-5611
> ------------------------------------------------------------------------------------------------
>
> Key: YARN-5865
> URL: https://issues.apache.org/jira/browse/YARN-5865
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Sunil G
> Assignee: Sunil G
> Attachments: YARN-5865.0001.patch, YARN-5865.0002.patch
>
>
> Post YARN-5611, revisit dynamic update of application priority logic with
> respect to state store error handling.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
