GitHub user zentol opened a pull request:
https://github.com/apache/flink/pull/2287
[hotfix] Prevent CheckpointCommitter from failing job
This PR fixes an issue in the `GenericWriteAheadSink` that @aljoscha
stumbled upon.
If the sink fails while writing the data into the external storage the sink
retries again on the next notify; it will never fail the job. However, the
CheckpointCommitter does not behave that way; if the storage cannot be queried
it will throw an exception that is not catched by the sink.
The exceptions are now catched and logged by the sink.
@aljoscha Could you try out whether this fixes the issue?
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zentol/flink cass_cc_failure
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/2287.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 #2287
----
commit e6c69b5c165489ea513ac134ff9801c78e88e948
Author: zentol <[email protected]>
Date: 2016-07-22T15:50:10Z
[hotfix] Prevent CheckpointCommitter from failing job
Prevents the CheckpointCommitter from failing a job, if either
commitCheckpoint() or isCheckpointCommitter() failed. Instead, we will
try again on the next notify().
----
---
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.
---
