[
https://issues.apache.org/jira/browse/FLINK-1484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14311988#comment-14311988
]
ASF GitHub Bot commented on FLINK-1484:
---------------------------------------
Github user tillrohrmann commented on the pull request:
https://github.com/apache/flink/pull/368#issuecomment-73479833
Yes, I'll do it.
On Mon, Feb 9, 2015 at 10:23 AM, Stephan Ewen <notificati...@github.com>
wrote:
> My bad, there is a ticket already. Can you squash the commits then and add
> the ticket tag?
>
> Otherwise, good to merge!
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/apache/flink/pull/368#issuecomment-73478622>.
>
> 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)
