[ https://issues.apache.org/jira/browse/YARN-5609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15512144#comment-15512144 ]
Arun Suresh commented on YARN-5609: ----------------------------------- bq. during rollback, we should not merge the current resourceSet with new one.. it should just be replaced Oops.. I meant _restart_ instead of _rollback_. in the case of a restart (if there exists a rollback state when the restart is called), both old and new Launch contexts are non-null, so in v006, it used to merge it.. now it doesnt. I know the {{isRollback}} boolean is not really needed... but I thought it makes the code clearer.. > Expose upgrade and restart API in ContainerManagementProtocol > ------------------------------------------------------------- > > Key: YARN-5609 > URL: https://issues.apache.org/jira/browse/YARN-5609 > Project: Hadoop YARN > Issue Type: Sub-task > Reporter: Arun Suresh > Assignee: Arun Suresh > Attachments: YARN-5609.001.patch, YARN-5609.002.patch, > YARN-5609.003.patch, YARN-5609.004.patch, YARN-5609.005.patch, > YARN-5609.006.patch, YARN-5609.007.patch, YARN-5609.008.patch > > > YARN-5620 and YARN-5637 allows an AM to explicitly *upgrade* a container with > a new launch context and subsequently *rollback* / *commit* the change on the > Container. This can also be used to simply *restart* the Container as well. > This JIRA proposes to extend the ContainerManagementProtocol with the > following API: > * *reInitializeContainer* > * *rollbackLastUpgrade* > * *commitLastUpgrade* > * *restartContainer* -- 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