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 2017/04/28 09:54:04 UTC
[jira] [Resolved] (FLINK-3347) TaskManager (or its ActorSystem)
need to restart in case they notice quarantine
[ https://issues.apache.org/jira/browse/FLINK-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Till Rohrmann resolved FLINK-3347.
----------------------------------
Resolution: Fixed
Fix Version/s: 1.3.0
Added via
1.3.0: bdf5c486f50b262dc09678a6c15790c54aa85240
1.2.0: 1ea252a
1.1.4: 16e7c78
> TaskManager (or its ActorSystem) need to restart in case they notice quarantine
> -------------------------------------------------------------------------------
>
> Key: FLINK-3347
> URL: https://issues.apache.org/jira/browse/FLINK-3347
> Project: Flink
> Issue Type: Improvement
> Components: Distributed Coordination
> Affects Versions: 0.10.1
> Reporter: Stephan Ewen
> Assignee: Till Rohrmann
> Priority: Critical
> Fix For: 1.3.0, 1.1.4, 1.2.0, 1.0.0
>
>
> There are cases where Akka quarantines remote actor systems. In that case, no further communication is possible with that actor system unless one of the two actor systems is restarted.
> The result is that a TaskManager is up and available, but cannot register at the JobManager (Akka refuses connection because of the quarantined state), making the TaskManager a useless process.
> I suggest to let the TaskManager restart itself once it notices that either it quarantined the JobManager, or the JobManager quarantined it.
> It is possible to recognize that by listening to certain events in the actor system event stream: http://stackoverflow.com/questions/32471088/akka-cluster-detecting-quarantined-state
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)