[
https://issues.apache.org/jira/browse/YARN-5609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15502625#comment-15502625
]
Jian He edited comment on YARN-5609 at 9/19/16 7:51 AM:
--------------------------------------------------------
Also, I plan to use HADOOP-11552 for the relocalize API in NMClient so that AM
does not need to poll for the completion of localization. Basically, the API
will block until the localization is asynchronously done. Does this make sense
for upgrade too ?
was (Author: jianhe):
Also, I plan to use HADOOP-11552 for the relocalize API so that AM does not
need to poll for the completion of localization. Basically, the API will block
until the localization is asynchronously done. Does this make sense for
upgrade too ?
> 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
>
> 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:
> * *upgradeContainer*
> * *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
