[
https://issues.apache.org/jira/browse/FLINK-13497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16898822#comment-16898822
]
vinoyang commented on FLINK-13497:
----------------------------------
[~SleePy] I discussed with [~yunta]. Yes, your analysis is correct.
My thought contains two points:
# Accept your point 2, just fail(cancel) an Execution instead of failing
globally;
# Bring state management for {{CheckpointFailureManager}} , define a field to
represent its state, let it has a lifecycle and start/stop with checkpoint
scheduler.
WDYT? cc [~till.rohrmann]
> 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)
