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-4876) [Phase 1] Decouple Container Init / Destroy from Start / Stop
Date Tue, 05 Apr 2016 19:14:25 GMT

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

Arun Suresh updated YARN-4876:
------------------------------
    Description: 
Introduce *initialize* and *destroy* container API into the *ContainerManagementProtocol*
so decouple the actual start of a container from the initialization. This will allow AMs to
re-initialize and re-start a container without having to lose the allocation.

Additionally, if the localization of the container is assicoated to the initialize (and the
cleanup with the destroy), This can also be used by applications to upgrade a Container by
re-initializing with a new *ContainerLaunchContext*

> [Phase 1] Decouple Container Init / Destroy from Start / Stop
> -------------------------------------------------------------
>
>                 Key: YARN-4876
>                 URL: https://issues.apache.org/jira/browse/YARN-4876
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Arun Suresh
>            Assignee: Arun Suresh
>
> Introduce *initialize* and *destroy* container API into the *ContainerManagementProtocol*
so decouple the actual start of a container from the initialization. This will allow AMs to
re-initialize and re-start a container without having to lose the allocation.
> Additionally, if the localization of the container is assicoated to the initialize (and
the cleanup with the destroy), This can also be used by applications to upgrade a Container
by re-initializing with a new *ContainerLaunchContext*



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message