[FLINK-10855] CheckpointCoordinator does not delete checkpoint directory of late/failed checkpoints

• Type: Bug
• Status: Open
• Priority: Not a Priority
• Resolution: Unresolved
• Affects Version/s: 1.5.5, 1.6.2, 1.7.0
• Component/s: Runtime / Checkpointing
• Labels: auto-deprioritized-major auto-deprioritized-minor auto-unassigned
• Assignee: Unassigned
• Reporter: Till Rohrmann
• Created: 12/Nov/18 16:03
• Updated: 26/Dec/21 10:39

Description

In case that an acknowledge checkpoint message is late or a checkpoint cannot be acknowledged, we discard the subtask state in the CheckpointCoordinator. What's not happening in this case is that we delete the parent directory of the checkpoint. This only happens when we dispose a PendingCheckpoint#dispose.

Due to this behaviour it can happen that a checkpoint fails (e.g. a task not being ready) and we delete the checkpoint directory. Next another task writes its checkpoint data to the checkpoint directory (thereby creating it again) and sending an acknowledge message back to the CheckpointCoordinator. The CheckpointCoordinator will realize that there is no longer a PendingCheckpoint and will discard the sub task state. This will remove the state files from the checkpoint directory but will leave the checkpoint directory untouched.

Issue Links

• is related to: FLINK-11662 Discarded checkpoint can cause Tasks to fail
• is related to: FLINK-10930 Refactor checkpoint directory layout
• links to: Checkpoint Storage cleanup improvement