Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Wed, 8 Jan 2014 06:45:56 +0000 (UTC)
From: "Jian He (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12662443.1375897089969.60032.1389163556125@arcas>
In-Reply-To: <JIRA.12662443.1375897089969@arcas>
References: <JIRA.12662443.1375897089969@arcas>
Subject: [jira] [Commented] (YARN-1041) Protocol changes for RM to bind and
 notify a restarted AM of existing containers
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jian He commented on YARN-1041:
-------------------------------

thanks for the comments, will update the patch once YARN-1490 gets in 

> Protocol changes for RM to bind and notify a restarted AM of existing containers
> --------------------------------------------------------------------------------
>
>                 Key: YARN-1041
>                 URL: https://issues.apache.org/jira/browse/YARN-1041
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>    Affects Versions: 3.0.0
>            Reporter: Steve Loughran
>            Assignee: Jian He
>         Attachments: YARN-1041.1.patch
>
>
> For long lived containers we don't want the AM to be a SPOF.
> When the RM restarts a (failed) AM, it should be given the list of containers it had already been allocated. the AM should then be able to contact the NMs to get details on them. NMs would also need to do any binding of the containers needed to handle a moved/restarted AM.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)