[ https://issues.apache.org/jira/browse/FLINK-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15611647#comment-15611647 ]
ASF GitHub Bot commented on FLINK-3347: --------------------------------------- Github user StephanEwen commented on the issue: https://github.com/apache/flink/pull/2697 Looks good to me. I would suggest to rename `taskmanager.quarantine-monitor.enable` to make it more accessible to users (few will understand what quarantine means). We could call it `taskmanager.exit-on-fatal-akka-error` or so. Otherwise +1 to merge this > 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: TaskManager > Affects Versions: 0.10.1 > Reporter: Stephan Ewen > Assignee: Till Rohrmann > Priority: Critical > Fix For: 1.0.0, 1.2.0, 1.1.4 > > > 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.4#6332)