[
https://issues.apache.org/jira/browse/YARN-1041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13895069#comment-13895069
]
Hudson commented on YARN-1041:
------------------------------
SUCCESS: Integrated in Hadoop-trunk-Commit #5130 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/5130/])
YARN-1493,YARN-1490,YARN-1041, YARN-1166,YARN-1566,YARN-1689,YARN-1661 are
reverted from branch-2.3. Updating YARN's CHANGES.txt. (vinodkv:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1565805)
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
> 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
> Fix For: 2.4.0
>
> Attachments: YARN-1041.1.patch, YARN-1041.2.patch, YARN-1041.3.patch,
> YARN-1041.4.patch, YARN-1041.5.patch, YARN-1041.6.patch, YARN-1041.7.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)
