hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1041) Protocol changes for RM to bind and notify a restarted AM of existing containers
Date Sat, 11 Jan 2014 07:02:51 GMT

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

Vinod Kumar Vavilapalli commented on YARN-1041:
-----------------------------------------------

TestResourceTrackerService failure is unrelated and happening on trunk too randomly. Will
file a ticket and debut this.

Checking this 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, 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)

Mime
View raw message