[
https://issues.apache.org/jira/browse/YARN-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13844594#comment-13844594
]
Hitesh Shah commented on YARN-1040:
-----------------------------------
Given the recent comments on YARN-1404, I believe that this should not be
supported unless the resources are being delegated to another YARN container.
Furthermore, if we are talking about container leases ( for multiple process
launches and not doing any resource delegation ), a container lease should
start when the first process is launched - thereby having an API that supports
a null ContainerLaunchContext is moot. The lease aspects should probably be
encoded into the container token so that the NM understands that a process
exiting in a particular container need not signal the end of the container i.e.
multipleProcesses should not be an explicit flag in the api.
> 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.4#6159)
