[ https://issues.apache.org/jira/browse/FLINK-3800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15344263#comment-15344263 ]
ASF GitHub Bot commented on FLINK-3800: --------------------------------------- Github user uce commented on a diff in the pull request: https://github.com/apache/flink/pull/2096#discussion_r68046896 --- Diff: flink-runtime/src/test/resources/log4j-test.properties --- @@ -16,7 +16,7 @@ # limitations under the License. ################################################################################ -log4j.rootLogger=OFF, console +log4j.rootLogger=INFO, console --- End diff -- Should stay `OFF`? > ExecutionGraphs can become orphans > ---------------------------------- > > Key: FLINK-3800 > URL: https://issues.apache.org/jira/browse/FLINK-3800 > Project: Flink > Issue Type: Bug > Components: JobManager > Affects Versions: 1.0.0, 1.1.0 > Reporter: Till Rohrmann > Assignee: Till Rohrmann > > The {{JobManager.cancelAndClearEverything}} method fails all currently > executed jobs on the {{JobManager}} and then clears the list of > {{currentJobs}} kept in the JobManager. This can become problematic if the > user has set a restart strategy for a job, because the {{RestartStrategy}} > will try to restart the job. This can lead to unwanted re-deployments of the > job which consumes resources and thus will trouble the execution of other > jobs. If the restart strategy never stops, then this prevents that the > {{ExecutionGraph}} from ever being properly terminated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)