[jira] [Closed] (FLINK-9417) Send heartbeat requests from RPC endpoint's main thread

["Till Rohrmann (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-9417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Till Rohrmann closed FLINK-9417.
--------------------------------
    Resolution: Duplicate

> Send heartbeat requests from RPC endpoint's main thread
> -------------------------------------------------------
>
>                 Key: FLINK-9417
>                 URL: https://issues.apache.org/jira/browse/FLINK-9417
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Coordination
>    Affects Versions: 1.5.0, 1.6.0
>            Reporter: Till Rohrmann
>            Assignee: Sihua Zhou
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)