Details
-
Sub-task
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
Reviewed
Description
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
Attachments
Attachments
Issue Links
- is related to
-
YARN-737 Some Exceptions no longer need to be wrapped by YarnException and can be directly thrown out after YARN-142
- Closed
-
YARN-618 Modify RM_INVALID_IDENTIFIER to a -ve number
- Closed
- relates to
-
MAPREDUCE-5167 Update MR App after YARN-562
- Closed
-
YARN-495 Change NM behavior of reboot to resync
- Closed