You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Andrew Wang (JIRA)" <ji...@apache.org> on 2016/10/18 21:50:59 UTC
[jira] [Updated] (YARN-5609) Expose upgrade and restart API in
ContainerManagementProtocol
[ https://issues.apache.org/jira/browse/YARN-5609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Wang updated YARN-5609:
------------------------------
Fix Version/s: 3.0.0-alpha2
As a reminder, please set a 3.x fix version when committing too. Thanks!
> 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
> Fix For: 2.9.0, 3.0.0-alpha2
>
> 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-5609.009.patch, YARN-5609.010.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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org