You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2016/06/23 16:12:16 UTC
[jira] [Closed] (FLINK-3800) ExecutionGraphs can become orphans
[ https://issues.apache.org/jira/browse/FLINK-3800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Till Rohrmann closed FLINK-3800.
--------------------------------
Resolution: Fixed
Fixed via 6420c1c264ed3ce0c32ba164c2cdb85ccdccf265
> 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)