You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (Jira)" <ji...@apache.org> on 2021/07/16 07:15:00 UTC
[jira] [Reopened] (FLINK-23209) Timeout heartbeat if the heartbeat
target is no longer reachable
[ https://issues.apache.org/jira/browse/FLINK-23209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Till Rohrmann reopened FLINK-23209:
-----------------------------------
> Timeout heartbeat if the heartbeat target is no longer reachable
> ----------------------------------------------------------------
>
> Key: FLINK-23209
> URL: https://issues.apache.org/jira/browse/FLINK-23209
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Affects Versions: 1.13.1, 1.12.4
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.14.0
>
>
> With FLINK-23202 it should now be possible to see when a remote RPC endpoint is no longer reachable. This can be used by the {{HeartbeatManager}} to mark an heartbeat target as no longer reachable. That way, it is possible for Flink to react faster to losses of components w/o having to wait for the heartbeat timeout to expire. This will result in faster recoveries (e.g. if a {{TaskExecutor}} dies).
> With this change we can improve trading off speed of detecting dead {{TaskManagers}} against running on an unstable/overloaded network where heartbeat messages are delayed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)