flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From uce <...@git.apache.org>
Subject [GitHub] flink pull request #2652: [FLINK-4715] Fail TaskManager with fatal error if ...
Date Mon, 17 Oct 2016 16:53:03 GMT
GitHub user uce opened a pull request:


    [FLINK-4715] Fail TaskManager with fatal error if task cancellation is stuck

    - Splits the cancellation up into two threads:
        * The `TaskCanceler` calls `cancel` on the invokable and `interrupt` on the executing
Thread. It then exists.
       * The `TaskCancellationWatchDog` kicks in after the task cancellation timeout (current
default: 30 secs) and periodically calls `interrupt` on the executing Thread. If the Thread
does not terminate within the task cancellation timeout (new config value, default 3 mins),
the task manager is notified about a fatal error, leading to termination of the JVM.
    - The new configuration is exposed via `ConfigConstants.TASK_CANCELLATION_TIMEOUT_MILLIS`
      (default: 3 mins) and the `ExecutionConfig` (similar to the cancellation interval).

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/uce/flink 4715-suicide

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2652


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.

View raw message