hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun Suresh (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-5609) Expose upgrade and restart API in ContainerManagementProtocol
Date Fri, 23 Sep 2016 09:07:20 GMT

     [ https://issues.apache.org/jira/browse/YARN-5609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Arun Suresh updated YARN-5609:
------------------------------
    Attachment: YARN-5609.009.patch

Uploading patch

bq. I think wherever setIsReInitializing(false) is called endReInitingContainer should be
called. Otherwise it's possible endReInitingContainer is not invoked.
Agreed... fixed this in v009

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


Mime
View raw message