Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Wed, 13 Nov 2013 18:01:26 +0000 (UTC)
From: "Alejandro Abdelnur (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12662436.1375896716831.67783.1384365686280@arcas>
In-Reply-To: <JIRA.12662436.1375896716831@arcas>
References: <JIRA.12662436.1375896716831@arcas>
Subject: [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
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

[~bikassaha], if I got it right, you suggest:

* {{StartContainerRequest}} would have a new property {{boolean multipleProcesses (false)}}
* An additional API {{startProcess(ContainerId, ContainerLaunchContext)}} will be used to start multiple processes within the same container.
* In a {{StartContainerRequest}}, if the {{ContainerLaunchContext == null}} and {{multipleProcesses = true}}, the container is started with no associated process and the container allocation will not timeout as it as been claimed by the AM (because of the start container request).

If that is the case, then YARN-1404 would be a special case of this JIRA.

Am i right?

> 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)