flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-3800) ExecutionGraphs can become orphans
Date Thu, 23 Jun 2016 13:11:16 GMT

    [ https://issues.apache.org/jira/browse/FLINK-3800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15346404#comment-15346404

ASF GitHub Bot commented on FLINK-3800:

Github user tillrohrmann commented on the issue:

    Will be merging this PR.

> 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

View raw message