Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Mon, 14 Apr 2014 16:34:17 +0000 (UTC)
From: "Jason Lowe (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12675104.1382469543327.110671.1397493257005@arcas>
In-Reply-To: <JIRA.12675104.1382469543327@arcas>
References: <JIRA.12675104.1382469543327@arcas>
Subject: [jira] [Assigned] (YARN-1337) Recover active container state upon
 nodemanager restart
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/YARN-1337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Lowe reassigned YARN-1337:
--------------------------------

    Assignee: Jason Lowe

> Recover active container state upon nodemanager restart
> -------------------------------------------------------
>
>                 Key: YARN-1337
>                 URL: https://issues.apache.org/jira/browse/YARN-1337
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: nodemanager
>    Affects Versions: 2.3.0
>            Reporter: Jason Lowe
>            Assignee: Jason Lowe
>
> To support work-preserving NM restart we need to recover the state of the containers that were active when the nodemanager went down.  This includes informing the RM of containers that have exited in the interim and a strategy for dealing with the exit codes from those containers along with how to reacquire the active containers and determine their exit codes when they terminate.


--
This message was sent by Atlassian JIRA
(v6.2#6252)