[FLINK-12619] Support TERMINATE/SUSPEND Job with Checkpoint

• Type: New Feature
• Status: Closed
• Priority: Minor
• Resolution: Won't Do
• Component/s: Runtime / State Backends
• Labels: auto-deprioritized-major auto-unassigned pull-request-available
• Assignee: Unassigned
• Reporter: Congxian Qiu
• Created: 24/May/19 12:43
• Updated: 13/Dec/21 14:28
• Resolved: 13/Dec/21 14:28

Description

Inspired by the idea of FLINK-11458, we propose to support terminate/suspend a job with checkpoint. This improvement cooperates with incremental and external checkpoint features, that if checkpoint is retained and this feature is configured, we will trigger a checkpoint before the job stops. It could accelarate job recovery a lot since:
1. No source rewinding required any more.
2. It's much faster than taking a savepoint since incremental checkpoint is enabled.

Please note that conceptually savepoints is different from checkpoint in a similar way that backups are different from recovery logs in traditional database systems. So we suggest using this feature only for job recovery, while stick with FLINK-11458 for the upgrading/cross-cluster-job-migration/state-backend-switch cases.

Issue Links

• is superceded by: FLINK-25276 FLIP-203: Support native and incremental savepoints
• is superceded by: FLINK-25154 FLIP-193: Snapshots ownership
• relates to: FLINK-6755 Allow triggering Checkpoints through command line client
• links to: GitHub Pull Request #8617
• links to: Stop-with-checkpoint
• mentioned in: Page Loading...

Sub-Tasks

• Expose Rest API for TERMINATE/SUSPEND Job with Checkpoint: Open