hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sunil G (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-5865) Retrospect updateApplicationPriority api to handle state store exception in align with YARN-5611
Date Mon, 14 Nov 2016 16:46:58 GMT

     [ https://issues.apache.org/jira/browse/YARN-5865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sunil G updated YARN-5865:
--------------------------
    Attachment: YARN-3955.0003.patch

Yes [~rohithsharma]. {{future}} needs to be set as null in case of any in b/w returns.

Also there were many places we were using {{submissionContext.getPriority}}. All such use
cases are moved to {{app.getApplicationPriority}}. So submission is used only in init/recover
cases. also while storing to StateStore.  hence patch is slightly bigger, but there is a lot
of good cleaning up has done.

pls help to check the same .

> 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-3955.0003.patch, 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: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message