GitHub user uce opened a pull request:
https://github.com/apache/flink/pull/2276
[FLINK-4201] [runtime] Forward suspend to checkpoint coordinator
Suspended jobs were leading to shutdown of the checkpoint coordinator and
hence removal of checkpoint state. For standalone recovery mode this is OK as
no state can be recovered anyways (unchanged in this PR). For HA though this
lead to removal of checkpoint state, which we
actually want to keep for recovery.
We have the following behaviour now:
JobState | Standalone | High Availability
-----------|------------|-------------------
SUSPENDED | Discard | Keep
FINISHED/FAILED/CANCELED | Discard | Discard
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/uce/flink 4201-discard_checkpoint
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/2276.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 #2276
----
commit 65bec557bafcfcfd53b6246f0a2154d259b0d6dd
Author: Ufuk Celebi <[email protected]>
Date: 2016-07-19T14:30:23Z
[FLINK-4201] [runtime] Forward suspend to checkpoint coordinator
Suspended jobs were leading to shutdown of the checkpoint coordinator
and hence removal of checkpoint state. For standalone recovery mode
this is OK as no state can be recovered anyways (unchanged in this PR).
For HA though this lead to removal of checkpoint state, which we
actually want to keep for recovery.
We have the following behaviour now:
-----------+------------+-------------------
| Standalone | High Availability
-----------+------------+-------------------
SUSPENDED | Discard | Keep
-----------+------------+-------------------
FINISHED/ | Discard | Discard
FAILED/ | |
CANCELED | |
-----------+------------+-------------------
----
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
