[
https://issues.apache.org/jira/browse/FLINK-10074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16618793#comment-16618793
]
ASF GitHub Bot commented on FLINK-10074:
----------------------------------------
tillrohrmann commented on issue #6567: [FLINK-10074] Allowable number of
checkpoint failures
URL: https://github.com/apache/flink/pull/6567#issuecomment-422329293
A failure of a global checkpoint should only increment the failure count by
one independent of the number of failed subtasks. Thus, I would hope that one
does not need to set a different threshold for the two different cases you
described @tweise. However, it is correct that the price the user pays is that
a consistent problem will only be detected after a longer delay.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> 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
> Labels: pull-request-available
>
> 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)
