You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2016/03/02 02:20:18 UTC
[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
[ https://issues.apache.org/jira/browse/YARN-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15174775#comment-15174775 ]
Vinod Kumar Vavilapalli commented on YARN-1040:
-----------------------------------------------
bq. General case: AM launches multiple containers at the same time. This is essentially container-groups - we should keep this option open.
Clarification on what I meant here: It's okay for now to only design APIs (and defer implementation) so that even if our first version of implementation only covers allocation-vs-container delinking, container-groups are possible in future without further API changes/addition.
> 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.3.4#6332)