[
https://issues.apache.org/jira/browse/FLINK-3443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15152742#comment-15152742
]
ASF GitHub Bot commented on FLINK-3443:
---------------------------------------
Github user uce commented on a diff in the pull request:
https://github.com/apache/flink/pull/1669#discussion_r53354572
--- Diff:
flink-runtime/src/main/scala/org/apache/flink/runtime/jobmanager/JobManager.scala
---
@@ -259,7 +259,7 @@ class JobManager(
// shut down the extra thread pool for futures
executorService.shutdown()
- log.debug(s"Job manager ${self.path} is completely stopped.")
+ log.info(s"Job manager ${self.path} is completely stopped.")
--- End diff --
I think this is OK to log on INFO (change was not by accident)
> JobManager cancel and clear everything fails jobs instead of cancelling
> -----------------------------------------------------------------------
>
> Key: FLINK-3443
> URL: https://issues.apache.org/jira/browse/FLINK-3443
> Project: Flink
> Issue Type: Bug
> Components: Distributed Runtime
> Reporter: Ufuk Celebi
> Assignee: Ufuk Celebi
>
> When the job manager is shut down, it calls {{cancelAndClearEverything}}.
> This method does not {{cancel}} the {{ExecutionGraph}} instances, but
> {{fail}}s them, which can lead to {{ExecutionGraph}} restart.
> I've noticed this in tests, where old graph got into a loop of restarts.
> What I don't understand is why the futures etc. are not cancelled when the
> executor service is shut down.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
