[
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.0006.patch
Thanks [~rohithsharma]
bq.After current patch change, you can remove
app.getApplicationSubmissionContext();
we need this variable to see whether its an unmanaged AM or not. But I think i
can move this variable to the statement where its used.
bq.Return type of API has changed from void to Priority. I am not sure does it
breaks
I think its fine as we have not released 2.8 yet provided we can push this jira
to 2.8. Thoughts?
Addressed all other comments.
> 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,
> YARN-5865.0003.patch, YARN-5865.0004.patch, YARN-5865.0005.patch,
> YARN-5865.0006.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]
