[ https://issues.apache.org/jira/browse/YARN-5620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arun Suresh updated YARN-5620: ------------------------------ Attachment: YARN-5620.004.patch [~jianhe], As per your suggestion, I am uploading a patch with just the restart container for your review convenience. I renamed it *reInitialize* to signify that the restart is dependent on the container being re-initialized with new bits. But, as per my previous comments, I do believe that we should not expose an upgrade without a rollback to just previous launch context (both implicit based on failure policy and well as an explicit rollback API). I would thus prefer to update the same JIRA with the rollback and commit calls (once you are satisfied with the restart flow) rather than open separate JIRAs. bq. the slider AM (also Yarn code) will have the prior context and call the upgardeContainer with the corresponding context, and so NM does not need to remember prior context. Hmmmm... I still believe rollback to just prior version should be supported by the NM.. and for rolling upgrades, atleast for production environments I have had experience with, it is an absolute requirement. The AM (Slider in our case) can subsequently _reinitialize_ to any version it chooses later on if it wants. > Core changes in NodeManager to support for upgrade and rollback of Containers > ----------------------------------------------------------------------------- > > Key: YARN-5620 > URL: https://issues.apache.org/jira/browse/YARN-5620 > Project: Hadoop YARN > Issue Type: Sub-task > Reporter: Arun Suresh > Assignee: Arun Suresh > Attachments: YARN-5620.001.patch, YARN-5620.002.patch, > YARN-5620.003.patch, YARN-5620.004.patch > > > JIRA proposes to modify the ContainerManager (and other core classes) to > support upgrade of a running container with a new {{ContainerLaunchContext}} > as well as the ability to rollback the upgrade if the container is not able > to restart using the new launch Context. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org