[
https://issues.apache.org/jira/browse/FLINK-4810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889872#comment-15889872
]
ASF GitHub Bot commented on FLINK-4810:
---------------------------------------
Github user ramkrish86 commented on the issue:
https://github.com/apache/flink/pull/3334
I think I got what you are saying here. Since Execution#triggerCheckpoint
is the actual checkpoint call and currently we don't track it if there is a
failure. So your point is it is better know if there was a failure in actual
checkpoint triggering at the Task level and then count that as a failure. Am I
right @wenlong88 ?
> Checkpoint Coordinator should fail ExecutionGraph after "n" unsuccessful
> checkpoints
> ------------------------------------------------------------------------------------
>
> Key: FLINK-4810
> URL: https://issues.apache.org/jira/browse/FLINK-4810
> Project: Flink
> Issue Type: Sub-task
> Components: State Backends, Checkpointing
> Reporter: Stephan Ewen
>
> The Checkpoint coordinator should track the number of consecutive
> unsuccessful checkpoints.
> If more than {{n}} (configured value) checkpoints fail in a row, it should
> call {{fail()}} on the execution graph to trigger a recovery.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
