[
https://issues.apache.org/jira/browse/FLINK-1484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14327635#comment-14327635
]
ASF GitHub Bot commented on FLINK-1484:
---------------------------------------
GitHub user tillrohrmann opened a pull request:
https://github.com/apache/flink/pull/423
[FLINK-1484] [FLINK-1499] Adds explicit disconnect messages in case of an
actor shutdown
Introduces explicit disconnect messages which are sent from the
JobManager/TaskManager to the TaskManager/JobManager in case of a graceful
actor termination. These disconnect messages allow a faster recovery from
failure in order to reach quickly a clean state.
Contains minor Scala cleanups.
This PR is based on #419
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tillrohrmann/flink taskManagerDisconnect
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/423.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #423
----
commit 8cc604d61d75370972146333c5a016b5fcdddc77
Author: Till Rohrmann <trohrm...@apache.org>
Date: 2015-02-19T10:04:56Z
[FLINK-1584] [runtime][tests] Fixes TaskManagerFailsITCase by replacing the
TestingCluster with a ForkableFlinkMiniCluster
commit 21660683633df999b86a7240929e07b8935e17df
Author: Till Rohrmann <trohrm...@apache.org>
Date: 2015-02-17T14:54:42Z
[Flink-1484] [runtime] Adds explicit disconnect message for TaskManagers
commit b2ff739feb6915bb131d1aeac7ca772eb4f85cba
Author: Till Rohrmann <trohrm...@apache.org>
Date: 2015-02-17T15:36:34Z
[FLINK-1499] [runtime] TaskManager sends explicit disconnect message to
JobManager in case of shutdown
----
> JobManager restart does not notify the TaskManager
> --------------------------------------------------
>
> Key: FLINK-1484
> URL: https://issues.apache.org/jira/browse/FLINK-1484
> Project: Flink
> Issue Type: Bug
> Reporter: Till Rohrmann
>
> In case of a JobManager restart, which can happen due to an uncaught
> exception, the JobManager is restarted. However, connected TaskManager are
> not informed about the disconnection and continue sending messages to a
> JobManager with a reseted state.
> TaskManager should be informed about a possible restart and cleanup their own
> state in such a case. Afterwards, they can try to reconnect to a restarted
> JobManager.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
