[
https://issues.apache.org/jira/browse/FLINK-6027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-6027:
----------------------------------
Labels: auto-deprioritized-major auto-unassigned (was: auto-unassigned
stale-major)
Priority: Minor (was: Major)
This issue was labeled "stale-major" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Major, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> Ignore the exception thrown by the subsuming of old completed checkpoints
> -------------------------------------------------------------------------
>
> Key: FLINK-6027
> URL: https://issues.apache.org/jira/browse/FLINK-6027
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Checkpointing
> Reporter: Xiaogang Shi
> Priority: Minor
> Labels: auto-deprioritized-major, auto-unassigned
>
> When a checkpoint is added into the {{CompletedCheckpointStore}} via the
> method {{addCheckpoint()}}, the oldest checkpoints will be removed from the
> store if the number of stored checkpoints exceeds the given limit. The
> subsuming of old checkpoints may fail and make {{addCheckpoint()}} throw
> exceptions which are caught by {{CheckpointCoordinator}}. Finally, the states
> in the new checkpoint will be deleted by {{CheckpointCoordinator}}. Because
> the new checkpoint is still in the store, we may recover the job from the new
> checkpoint. But the recovery will fail as the states of the checkpoint are
> all deleted.
> We should ignore the exceptions thrown by the subsuming of old checkpoints
> because we can always recover from the new checkpoint when successfully
> adding it into the store. The ignorance may produce some dirty data, but it's
> acceptable because they can be cleaned with the cleanup hook introduced in
> the near future.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
