[
https://issues.apache.org/jira/browse/FLINK-13497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16897891#comment-16897891
]
Biao Liu commented on FLINK-13497:
----------------------------------
There is another problem. The {{failGlobal}} might fail the job in an
unexpected way. If the job has already restarted between the
{{declineCheckpoint}} and {{failGlobal}} (due to a task failure). The job would
restart again when this asynchronous {{failGlobal}} arrived. I think we should
not use {{failGlobal}} directly. Canceling a task (or tasks) with specific
{{ExecutionAttemptID}} might be better. It's also more friendly with other
failover strategy. For example if under "region failover" strategy, we could
avoid a global failover.
> Checkpoints can complete after CheckpointFailureManager fails job
> -----------------------------------------------------------------
>
> Key: FLINK-13497
> URL: https://issues.apache.org/jira/browse/FLINK-13497
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Checkpointing
> Affects Versions: 1.9.0, 1.10.0
> Reporter: Till Rohrmann
> Priority: Critical
> Fix For: 1.9.0
>
>
> I think that we introduced with FLINK-12364 an inconsistency wrt to job
> termination a checkpointing. In FLINK-9900 it was discovered that checkpoints
> can complete even after the {{CheckpointFailureManager}} decided to fail a
> job. I think the expected behaviour should be that we fail all pending
> checkpoints once the {{CheckpointFailureManager}} decides to fail the job.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
