[
https://issues.apache.org/jira/browse/YARN-4876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15291954#comment-15291954
]
Marco Rabozzi commented on YARN-4876:
-------------------------------------
Thanks [~vvasudev] for looking at the patch!
Regarding the allowsRestart() function, it refers to whether the AM is allowed
to issue multiple start or initialize requests for the container. If the AM
starts a container with the standard startContainers API, allowsRestart() will
return false and re-initialization or re-start won't be allowed reflecting the
current APIs behavior. On the other hand, if the AM uses the new
initializeContainers API, allowsRestart() will return true and the AM will be
able to issue multiple startContainers and initializeContainers requests for
the container.
> [Phase 1] 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
> Reporter: Arun Suresh
> Assignee: Marco Rabozzi
> Attachments: YARN-4876-design-doc.pdf, 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
(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
