[
https://issues.apache.org/jira/browse/YARN-5609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15508741#comment-15508741
]
Jian He commented on YARN-5609:
-------------------------------
bq. I had intentionally kept it that way (my thinking was that the Tracker will
then verify that the resources.. directories etc. are still good)
Yep, I also had that in mind for rollback. And I think it is indeed needed for
rollback, because the old resource may have a change to get purged...
But for restart, as the same resources are re-used, we don't need to re-check.
So, I guess we need to retain the behavior for rollback ?
> 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-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
