You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/02/20 15:45:44 UTC
[jira] [Commented] (FLINK-4944) Replace Akka's death watch with own
heartbeat on the TM side
[ https://issues.apache.org/jira/browse/FLINK-4944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874720#comment-15874720 ]
ASF GitHub Bot commented on FLINK-4944:
---------------------------------------
Github user tillrohrmann commented on the issue:
https://github.com/apache/flink/pull/2742
FYI @StephanEwen. Rebased onto the latest master.
> Replace Akka's death watch with own heartbeat on the TM side
> ------------------------------------------------------------
>
> Key: FLINK-4944
> URL: https://issues.apache.org/jira/browse/FLINK-4944
> Project: Flink
> Issue Type: Improvement
> Components: Distributed Coordination
> Affects Versions: 1.2.0
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
> Fix For: 1.3.0
>
>
> In order to properly implement FLINK-3347, the {{TaskManager}} must no longer use Akka's death watch mechanism to detect {{JobManager}} failures. The reason is that a hard {{JobManager}} failure will lead to quarantining the {{JobManager's}} {{ActorSystem}} by the {{TaskManagers}}. This in combination with FLINK-3347 would lead to a shutdown of all {{TaskManagers}}.
> Instead we should use our own heartbeat signal to detect dead {{JobManagers}}. In case of a heartbeat timeout, the {{TaskManager}} won't shut down but simply cancel and clear everything.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)