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 2015/02/05 21:06:34 UTC

[jira] [Commented] (FLINK-1484) JobManager restart does not notify the TaskManager

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

ASF GitHub Bot commented on FLINK-1484:
---------------------------------------

GitHub user tillrohrmann opened a pull request:

    https://github.com/apache/flink/pull/368

    [FLINK-1484] Adds explicit disconnect message for TaskManagers

    In case of a JobManager restart, which can be caused by an uncaught exception, all connected TaskManager are notified by a ```Disconnected``` message. This message triggers the cleanup of the TaskManagers and makes them try to reconnect to the JobManager.
    
    This PR also includes a test case to verify the afore-mentioned behaviour.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/tillrohrmann/flink akkaSupervision

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/368.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 #368
    
----
commit 081721a01b5070dccdc807bf3ecd14d5b9de1b24
Author: Till Rohrmann <tr...@apache.org>
Date:   2015-02-05T19:58:59Z

    Adds explicit disconnect message to tell TaskManagers that the JobManager has failed

----


> 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)