[YARN-3802] Two RMNodes for the same NodeId are used in RM sometimes after NM is reconnected.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.7.0
• Fix Version/s: 2.8.0, 2.7.2, 2.6.2, 3.0.0-alpha1
• Component/s: resourcemanager
• Assignee: Zhihai Xu Assign to me
• Reporter: Zhihai Xu
• Created: 14/Jun/15 22:36
• Updated: 06/Jan/17 01:41
• Resolved: 18/Jun/15 21:39

Description

Two RMNodes for the same NodeId are used in RM sometimes after NM is reconnected. Scheduler and RMContext use different RMNode reference for the same NodeId sometimes after NM is reconnected, which is not correct. Scheduler and RMContext should always use same RMNode reference for the same NodeId.

Issue Links

• is duplicated by: MAPREDUCE-6398 Two RMNodes for the same NodeId are used in RM sometimes after NM is reconnected.
• is related to: YARN-4344 NMs reconnecting with changed capabilities can lead to wrong cluster resource calculations
• is related to: YARN-4761 NMs reconnecting with changed capabilities can lead to wrong cluster resource calculations on fair scheduler