You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2016/11/18 13:46:58 UTC
[jira] [Created] (FLINK-5098) Detect network problems to eagerly
time out ask operations
Till Rohrmann created FLINK-5098:
------------------------------------
Summary: Detect network problems to eagerly time out ask operations
Key: FLINK-5098
URL: https://issues.apache.org/jira/browse/FLINK-5098
Project: Flink
Issue Type: Improvement
Components: Distributed Coordination
Affects Versions: 1.2.0
Reporter: Till Rohrmann
Assignee: Till Rohrmann
Fix For: 1.2.0
Akka's ask operations are given a timeout after which they should fail with an {{AskTimeoutException}}. In some cases, however, it is possible to fail early because one has detected that the remote host is not reachable or that the actor does not exist on the remote {{ActorSystem}}.
Usually failing early if one cannot hope for a successful message delivery is a desirable behaviour since it speeds up recovery.
I propose to send Akka's {{Identify}} message with each ask request. The identify message allows to detect unreachable/non-existing actors and, thus, enables us to fail the ask operation early.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)