[FLINK-13426] TaskExecutor uses the wrong Registrationid in the heartbeat with RM.

• Type: Bug
• Status: Reopened
• Priority: Not a Priority
• Resolution: Unresolved
• Affects Version/s: 1.8.1, 1.9.0
• Component/s: Runtime / Coordination
• Assignee: Unassigned
• Reporter: Guowei Ma
• Created: 25/Jul/19 09:51
• Updated: 29/Jul/21 07:36

Description

1. First-time TaskExecutor register to rm successfully. If it fails to send SlotReport to SlotMaanger, TaskExecutor will reconnect to RM again. However, TaskExecutor still uses the old registration id in the EstablishedResourceManagerConnection.

2. Second-time TaskExecutor registers to rm successfully and gets a new registration id.

3. First-round and second-round has a race condition. Since that the task executor maybe use the old registration id in heartbeat with rm.