[FLINK-9417] Send heartbeat requests from RPC endpoint's main thread

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 1.5.0, 1.6.0
• Component/s: Runtime / Coordination
• Labels: pull-request-available
• Assignee: Unassigned
• Reporter: Till Rohrmann
• Created: 23/May/18 07:24
• Updated: 28/Feb/20 10:51
• Resolved: 28/Feb/20 10:51

Description

Currently, we use the RpcService#scheduledExecutor to send heartbeat requests to remote targets. This has the problem that we still see heartbeats from this endpoint also if its main thread is currently blocked. Due to this, the heartbeat response cannot be processed and the remote target times out. On the remote side, this won't be noticed because it still receives the heartbeat requests.

A solution to this problem would be to send the heartbeat requests to the remote thread through the RPC endpoint's main thread. That way, also the heartbeats would be blocked if the main thread is blocked/busy.

Issue Links

• duplicates: FLINK-12863 Race condition between slot offerings and AllocatedSlotReport
• links to: GitHub Pull Request #6088
• links to: GitHub Pull Request #6088