[
https://issues.apache.org/jira/browse/FLINK-6315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15971404#comment-15971404
]
ASF GitHub Bot commented on FLINK-6315:
---------------------------------------
GitHub user sjwiesman opened a pull request:
https://github.com/apache/flink/pull/3729
[FLINK-6315] Notify on checkpoint timeout
https://issues.apache.org/jira/browse/FLINK-6315
A common use case when writing a custom operator that outputs data to some
third party location to partially output on checkpoint and then commit on
notifyCheckpointComplete. If that external system does not gracefully handle
rollbacks (such as Amazon S3 not allowing consistent delete operations) then
that data needs to be handled by the next checkpoint.
The idea is to add a new interface similar to CheckpointListener that
provides a callback when the CheckpointCoordinator times out a checkpoint
This is required for the eventually consistent sink coming in FLINK-6306 to
be able to differentiate between concurrent checkpoints and timed out
checkpoints.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sjwiesman/flink FLINK-6315
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/3729.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 #3729
----
commit 323851929772b4c57e65b7146e96af6687d3a2eb
Author: Seth Wiesman <[email protected]>
Date: 2017-04-15T21:13:20Z
FLINK-6315 Notify on checkpoint timeout
https://issues.apache.org/jira/browse/FLINK-6315
----
> Notify on checkpoint timeout
> -----------------------------
>
> Key: FLINK-6315
> URL: https://issues.apache.org/jira/browse/FLINK-6315
> Project: Flink
> Issue Type: New Feature
> Components: Core
> Reporter: Seth Wiesman
> Assignee: Seth Wiesman
>
> A common use case when writing a custom operator that outputs data to some
> third party location to partially output on checkpoint and then commit on
> notifyCheckpointComplete. If that external system does not gracefully handle
> rollbacks (such as Amazon S3 not allowing consistent delete operations) then
> that data needs to be handled by the next checkpoint.
> The idea is to add a new interface similar to CheckpointListener that
> provides a callback when the CheckpointCoordinator timesout a checkpoint
> {code:java}
> /**
> * This interface must be implemented by functions/operations that want to
> receive
> * a notification if a checkpoint has been {@link
> org.apache.flink.runtime.checkpoint.CheckpointCoordinator}
> */
> public interface CheckpointTimeoutListener {
> /**
> * This method is called as a notification if a distributed checkpoint
> has been timed out.
> *
> * @param checkpointId The ID of the checkpoint that has been timed out.
> * @throws Exception
> */
> void notifyCheckpointTimeout(long checkpointId) throws Exception;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
