[
https://issues.apache.org/jira/browse/YARN-891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jian He updated YARN-891:
-------------------------
Attachment: YARN-891.7.patch
bq. Is APP_SAVED event being overloaded for both saving initial and final
state?
Create a separate Update event specifically for update operation.
bq. Simply returning accepted state may not be enough since the scheduler has
to first actually accept the existing app attempt before it can be in accepted
state.
Correct, that will be done as part of YARN-1210, rephrase the comment.
bq. it looks like the following may change the final state from what was
originally intended to be the final state/what is stored as the final state
when the attempt first moved to final_saving state.
Fixed. in AMExpiredAtFinalSavingTransition and
ContainerFinishedAtFinalSavingTransition, return if it was supposed to reach
Failed/Killed state. Similarly in
RMAppImpl.AppFinishedFinalStateSavingTransition
> Store completed application information in RM state store
> ---------------------------------------------------------
>
> Key: YARN-891
> URL: https://issues.apache.org/jira/browse/YARN-891
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Reporter: Bikas Saha
> Assignee: Jian He
> Attachments: YARN-891.1.patch, YARN-891.2.patch, YARN-891.3.patch,
> YARN-891.4.patch, YARN-891.5.patch, YARN-891.6.patch, YARN-891.7.patch,
> YARN-891.patch, YARN-891.patch, YARN-891.patch, YARN-891.patch,
> YARN-891.patch, YARN-891.patch
>
>
> Store completed application/attempt info in RMStateStore when
> application/attempt completes. This solves some problems like finished
> application get lost after RM restart and some other races like YARN-1195
--
This message was sent by Atlassian JIRA
(v6.1#6144)
