Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DCB5C10ED6 for ; Tue, 12 Nov 2013 23:29:18 +0000 (UTC) Received: (qmail 97089 invoked by uid 500); 12 Nov 2013 23:29:18 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 97048 invoked by uid 500); 12 Nov 2013 23:29:18 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 97039 invoked by uid 99); 12 Nov 2013 23:29:18 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Nov 2013 23:29:18 +0000 Date: Tue, 12 Nov 2013 23:29:18 +0000 (UTC) From: "Alejandro Abdelnur (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: 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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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)