Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Mon, 14 Oct 2013 21:03:45 +0000 (UTC)
From: "Tsuyoshi OZAWA (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12673321.1381444042631.62015.1381784625939@arcas>
In-Reply-To: <JIRA.12673321.1381444042631@arcas>
References: <JIRA.12673321.1381444042631@arcas>
Subject: [jira] [Commented] (YARN-1292) De-link container life cycle from
 the process it runs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Tsuyoshi OZAWA commented on YARN-1292:
--------------------------------------

I see, then the NM-only change is required.

> De-link container life cycle from the process it runs
> -----------------------------------------------------
>
>                 Key: YARN-1292
>                 URL: https://issues.apache.org/jira/browse/YARN-1292
>             Project: Hadoop YARN
>          Issue Type: Improvement
>    Affects Versions: 2.1.1-beta
>            Reporter: Bikas Saha
>
> Currently, a container is considered done when its OS process exits. This makes it cumbersome for apps to be able to reuse containers for different processes. Long running daemons may want to run in the same containers as the previous versions. So eg. is an hbase region server crashes/upgraded it would want to restart in the same container where everything it needs would already be warm and ready.


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