[
https://issues.apache.org/jira/browse/FLINK-10074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16579327#comment-16579327
]
vinoyang commented on FLINK-10074:
----------------------------------
[~thw] The setFailOnCheckpointingErrors API is currently not marked as @Public,
but is also a public API, perhaps we should keep it for compatibility, but this
does confuse what the current issue needs to do. The
setFailOnCheckpointingErrors method provides two states, true or false. This
issue provides three states that are sufficient to override the functionality
of the setFailOnCheckpointingErrors method. How to decide? [~till.rohrmann].
The second question, you are right.
> Allowable number of checkpoint failures
> ----------------------------------------
>
> Key: FLINK-10074
> URL: https://issues.apache.org/jira/browse/FLINK-10074
> Project: Flink
> Issue Type: Improvement
> Components: State Backends, Checkpointing
> Reporter: Thomas Weise
> Assignee: vinoyang
> Priority: Major
>
> For intermittent checkpoint failures it is desirable to have a mechanism to
> avoid restarts. If, for example, a transient S3 error prevents checkpoint
> completion, the next checkpoint may very well succeed. The user may wish to
> not incur the expense of restart under such scenario and this could be
> expressed with a failure threshold (number of subsequent checkpoint
> failures), possibly combined with a list of exceptions to tolerate.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
