[
https://issues.apache.org/jira/browse/YARN-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13628250#comment-13628250
]
Vinod Kumar Vavilapalli commented on YARN-562:
----------------------------------------------
Yes, the easiest way to do this is to send the RM's cluster timestamp over to
NMs as part of registration. All containers have IDs anyways, so NMs can
validate the timestamps and reject any containers dished out by old RMs. This
is useful even for a failed over RM.
> NM should reject containers allocated by previous RM
> ----------------------------------------------------
>
> Key: YARN-562
> URL: https://issues.apache.org/jira/browse/YARN-562
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Reporter: Jian He
> Assignee: Jian He
>
> Its possible that after RM shutdown, before AM goes down,AM still call
> startContainer on NM with containers allocated by previous RM. When RM comes
> back, NM doesn't know whether this container launch request comes from
> previous RM or the current RM. we should reject containers allocated by
> previous RM
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
