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-3443) JobManager cancel and clear everything fails jobs instead of cancelling
Date Fri, 19 Feb 2016 20:58:18 GMT

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

ASF GitHub Bot commented on FLINK-3443:

Github user StephanEwen commented on a diff in the pull request:

    --- Diff: flink-runtime/src/main/scala/org/apache/flink/runtime/jobmanager/JobManager.scala
    @@ -1487,7 +1487,7 @@ class JobManager(
    -        eg.fail(cause)
    +        eg.cancel()
    --- End diff --
    I liked it that the job was not marked as "canceled()" (which gives no reason), but as
failed, with a cause. The cause also shows up in the TaskManager logs, when the Task was "externally
    Any specific reason that this changes? Is this currently inconsistent?

> 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

View raw message