[
https://issues.apache.org/jira/browse/FLINK-1484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14308938#comment-14308938
]
ASF GitHub Bot commented on FLINK-1484:
---------------------------------------
Github user mxm commented on a diff in the pull request:
https://github.com/apache/flink/pull/368#discussion_r24232671
--- Diff:
flink-runtime/src/main/scala/org/apache/flink/runtime/messages/TaskManagerMessages.scala
---
@@ -129,6 +129,13 @@ object TaskManagerMessages {
* @param cause reason for the external failure
*/
case class FailTask(executionID: ExecutionAttemptID, cause: Throwable)
+
+ /**
+ * Makes the TaskManager to disconnect from the registered JobManager
--- End diff --
Minor typo. Comment could be changed to "Disconnects the TaskManager from
the JobManager"
> 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)
