[ 
https://issues.apache.org/jira/browse/YARN-5609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15502735#comment-15502735
 ] 

Arun Suresh edited comment on YARN-5609 at 9/19/16 8:45 AM:
------------------------------------------------------------

Uploading initial patch:

* This includes all the protocol, PBImpl changes and any changes resulting in 
modifying the ContainerManagerProtocol.
* This does not contain the changes to {{NMClient}}.
* Decided to go with *reInitializeContainer* instead of *upgradeContainer*, 
since the API can very well be used to move back to any old version as long as 
a Launch context is provided.



was (Author: asuresh):
Uploading initial patch:

* This includes all the protocol, PBImpl changes and any changes resulting in 
modifying the ContainerManagerProtocol.
* This does not contain the changes to {{NMClient}}.


> 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-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

Reply via email to