[YARN-3286] Cleanup RMNode#ReconnectNodeTransition

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 2.6.0, 2.7.0
• Component/s: resourcemanager
• Assignee: Rohith Sharma K S
• Reporter: Rohith Sharma K S
• Created: 03/Mar/15 09:17
• Updated: 12/Nov/15 07:07
• Resolved: 09/Oct/15 04:48

Description

RMNode#ReconnectNodeTransition has messed up for every ReconnectedEvent. This part of the code can be clean up where we do not require to remove node and add new node every time.

Supporting to above point, in the issue discussion YARN-3222 mentioned in the comment link1 and link2

Clean up can do the following things

1. It always remove an old node and add a new node. This is not really required, instead old node can be updated with new values.
2. RMNode#totalCapability has stale capability after NM is reconnected.

Issue Links

• is related to: YARN-4344 NMs reconnecting with changed capabilities can lead to wrong cluster resource calculations