[
https://issues.apache.org/jira/browse/YARN-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13642482#comment-13642482
]
Bikas Saha commented on YARN-562:
---------------------------------
RM_INVALID_IDENTIFIER set to 0 doesnt sound right as many tests set it to 0.
Probably a -ve number is what we want. Looks good other than that.
Did we run a single node setup with a few jobs to do a real sanity check?
> 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.10.patch, YARN-562.11.patch, YARN-562.12.patch,
> YARN-562.1.patch, YARN-562.2.patch, YARN-562.3.patch, YARN-562.4.patch,
> YARN-562.5.patch, YARN-562.6.patch, YARN-562.7.patch, YARN-562.8.patch,
> YARN-562.9.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
