hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-4876) Decoupled Init / Destroy of Containers from Start / Stop
Date Thu, 27 Oct 2016 18:39:01 GMT

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

Jason Lowe updated YARN-4876:
         Labels: oct16-hard  (was: )
    Component/s: nodemanager

> Decoupled Init / Destroy of Containers from Start / Stop
> --------------------------------------------------------
>                 Key: YARN-4876
>                 URL: https://issues.apache.org/jira/browse/YARN-4876
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: api, nodemanager
>            Reporter: Arun Suresh
>            Assignee: Marco Rabozzi
>              Labels: oct16-hard
>         Attachments: YARN-4876-design-doc.pdf, YARN-4876.002.patch, YARN-4876.003.patch,
YARN-4876.004.patch, YARN-4876.01.patch
> Introduce *initialize* and *destroy* container API into the *ContainerManagementProtocol*
and decouple the actual start of a container from the initialization. This will allow AMs
to re-start a container without having to lose the allocation.
> Additionally, if the localization of the container is associated 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

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message