[FLINK-12836] Allow retained checkpoints to be persisted on success

• Type: Improvement
• Status: Open
• Priority: Not a Priority
• Resolution: Unresolved
• Component/s: Runtime / Checkpointing
• Labels: auto-deprioritized-major auto-deprioritized-minor auto-unassigned
• Assignee: Unassigned
• Reporter: Andrew Duffy
• Created: 13/Jun/19 13:47
• Updated: 22/Dec/21 10:39

Description

Currently, retained checkpoints are persisted with one of 3 strategies:

• CHECKPOINT_NEVER_RETAINED: Retained checkpoints are never persisted
• CHECKPOINT_RETAINED_ON_FAILURE: Latest retained checkpoint is persisted in the face of job failures
• CHECKPOINT_RETAINED_ON_CANCELLATION: Latest retained checkpoint is persisted when job is canceled externally (e.g. via the REST API)

 

I'm proposing a third persistence mode: CHECKPOINT_RETAINED_ALWAYS. This mode would ensure that retained checkpoints are retained on successful completion of the job, and can be resumed from later.