flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Metzger (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-4944) Replace Akka's death watch with own heartbeat on the TM side
Date Mon, 23 Jan 2017 12:17:26 GMT

    [ https://issues.apache.org/jira/browse/FLINK-4944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15834364#comment-15834364
] 

Robert Metzger commented on FLINK-4944:
---------------------------------------

I'm moving the JIRA to the 1.3.0 release. The merge window for 1.2.0 fixes is closed.

> 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: TaskManager
>    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.4#6332)

Mime
View raw message