GitHub user aljoscha opened a pull request:

    https://github.com/apache/flink/pull/1532

    [hotfix] Fix interaction of Async calls/checkpointing/canceling

    Before, it could happen that a Task is canceled during snapshotting.
    Some State Backends would silently swallow exceptions resulting from
    this and the Task would get stuck until the cleanup logic gets to it.
    
    Now, we rethrow a CancelTaskException if isRunning is false in
    StreamTask after performing snapshots.
    
    This also moves the logic that swallows exceptions in case a task is not
    running anymore from StreamTask to the async caller in Task.

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

    $ git pull https://github.com/aljoscha/flink cancel-exception-fix

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

    https://github.com/apache/flink/pull/1532.patch

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

    This closes #1532
    
----
commit ffa7534adf70af0c139a1d8195e49fe494e663e3
Author: Aljoscha Krettek <aljoscha.kret...@gmail.com>
Date:   2016-01-20T17:09:12Z

    [hotfix] Fix interaction of Async calls/checkpointing/canceling
    
    Before, it could happen that a Task is canceled during snapshotting.
    Some State Backends would silently swallow exceptions resulting from
    this and the Task would get stuck until the cleanup logic gets to it.
    
    Now, we rethrow a CancelTaskException if isRunning is false in
    StreamTask after performing snapshots.
    
    This also moves the logic that swallows exceptions in case a task is not
    running anymore from StreamTask to the async caller in Task.

----


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to