[
https://issues.apache.org/jira/browse/YARN-5637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun Suresh updated YARN-5637:
------------------------------
Attachment: YARN-5637.001.patch
Uploading initial patch based on the framework laid out in YARN-5620.
I havn't submitted the patch yet since it depends on YARN-5620.. will do once
that goes in.
[~jianhe], [~vvasudev]... do let me know what you think.
Some assumptions:
* AutoCommit is set to _true_ by default
* If _retryFailurePolicy_ is NOT specified, then the Container will be
terminated immediately if upgrade fails.
* If _retryFailurePolicy_ is specified, the upgraded Container will be
retried/relaunch as per the policy.. and if that fails... then container will
be rolledback to previous state.
* If _autoCommit_ is *false* and user has called the _commitUpgarde_ API, then
no rollback will be allowed after that.
* If _autoCommit_ is *true* then no Explicit or implicit (upgraded process
fails to start) rollback will be allowed.
> Changes in NodeManager to support Container upgrade and rollback/commit
> -----------------------------------------------------------------------
>
> Key: YARN-5637
> URL: https://issues.apache.org/jira/browse/YARN-5637
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Arun Suresh
> Assignee: Arun Suresh
> Attachments: YARN-5637.001.patch
>
>
> YARN-5620 added support for re-initialization of Containers using a new
> launch Context.
> This JIRA proposes to use the above feature to support upgrade and subsequent
> rollback or commit of the upgrade.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
