[FLINK-25154] FLIP-193: Snapshots ownership

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Implemented
• Fix Version/s: 1.15.0
• Component/s: Runtime / Checkpointing

Release Note

When restoring from a savepoint or retained externalized checkpoint you can choose the mode in which you want to perform the operation. You can choose from CLAIM, NO_CLAIM, LEGACY(the old behaviour).

In CLAIM mode Flink takes ownership of the snapshot and will potentially try to remove the snapshot at a certain point in time. On the other hand the NO_CLAIM mode will make sure Flink does not depend on the existence of any files belonging to the initial snapshot.

For a more thorough description see the documentaion.

• Assignee: Dawid Wysakowicz
• Reporter: Dawid Wysakowicz
• Created: 03/Dec/21 11:24
• Updated: 01/Feb/22 17:40
• Resolved: 01/Feb/22 17:40

Description

Task for implementing FLIP-193: https://cwiki.apache.org/confluence/x/bIyqCw

Issue Links

• is related to: FLINK-25887 FLIP-193: Snapshots ownership follow ups
• relates to: FLINK-24149 Make checkpoint self-contained and relocatable
• supercedes: FLINK-12619 Support TERMINATE/SUSPEND Job with Checkpoint

Sub-Tasks

• Implement claim snapshot mode: Closed
• Skip savepoints for recovery: Closed
• Implement proper no-claim mode support: Closed
• Document claim & no-claim mode: Closed
• Implement an API for duplicating artefacts: Closed