[ https://issues.apache.org/jira/browse/YARN-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13633215#comment-13633215 ]
Jian He commented on YARN-562: ------------------------------ cluster_timestamp here is merely the time recorded when RM starts, not a vector clock. All containers launched in the same RM would then have the same timestamp. Both approaches I think would work. Having the same stamp looks more clear. > 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 > Attachments: YARN-562.1.patch, YARN-562.2.patch, YARN-562.3.patch > > > 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