[jira] [Commented] (YARN-1040) De-link container life cycle from the process and add ability to execute multiple processes in the same long-lived container

["Alejandro Abdelnur (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/YARN-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13820645#comment-13820645 ] 

Alejandro Abdelnur commented on YARN-1040:
------------------------------------------

[~bikassaha], a minor twist to the outlined approach is that we don't need flag, just a NULL {{ContainerLaunchContext}} and that this context is not NULL on {{startContainer()}} the container is meant to have 1 process only and finishes on process completion. This would preserve backwards compatibility. Only when the startContainer has a NULL context, there could be multiple processes. Makes sense?

> De-link container life cycle from the process and add ability to execute multiple processes in the same long-lived container
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: YARN-1040
>                 URL: https://issues.apache.org/jira/browse/YARN-1040
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: nodemanager
>    Affects Versions: 3.0.0
>            Reporter: Steve Loughran
>
> The AM should be able to exec >1 process in a container, rather than have the NM automatically release the container when the single process exits.
> This would let an AM restart a process on the same container repeatedly, which for HBase would offer locality on a restarted region server.
> We may also want the ability to exec multiple processes in parallel, so that something could be run in the container while a long-lived process was already running. This can be useful in monitoring and reconfiguring the long-lived process, as well as shutting it down.



--
This message was sent by Atlassian JIRA
(v6.1#6144)