[FLINK-6755] Allow triggering Checkpoints through command line client

• Type: New Feature
• Status: Closed
• Priority: Not a Priority
• Resolution: Fixed
• Affects Version/s: 1.3.0
• Fix Version/s: 1.19.0
• Component/s: Command Line Client, Runtime / Checkpointing
• Labels: auto-deprioritized-major auto-unassigned pull-request-available

Release Note

Currently the command line interface support triggering a checkpoint manually. Usage:
  ./bin/flink checkpoint $JOB_ID [-full]
By specifying the '-full' option, a full checkpoint is triggered. Otherwise an incremental checkpoint is triggered if the job is configured to take incremental ones periodically.

• Assignee: Zakelly Lan
• Reporter: Gyula Fora
• Created: 29/May/17 08:23
• Updated: 21/Feb/24 05:03
• Resolved: 29/Nov/23 16:50

Description

The command line client currently only allows triggering (and canceling with) Savepoints.

While this is good if we want to fork or modify the pipelines in a non-checkpoint compatible way, now with incremental checkpoints this becomes wasteful for simple job restarts/pipeline updates.

I suggest we add a new command:
./bin/flink checkpoint <jobID> [checkpointDirectory]

and a new flag -c for the cancel command to indicate we want to trigger a checkpoint:
./bin/flink cancel -c [targetDirectory] <jobID>

Otherwise this can work similar to the current savepoint taking logic, we could probably even piggyback on the current messages by adding boolean flag indicating whether it should be a savepoint or a checkpoint.

Issue Links

• is related to: FLINK-24280 Support manual checkpoints triggering from a MiniCluster
• is related to: FLINK-25276 FLIP-203: Support native and incremental savepoints
• is related to: FLINK-12619 Support TERMINATE/SUSPEND Job with Checkpoint
• relates to: FLINK-27101 Add REST API to manually trigger checkpoints
• links to: GitHub Pull Request #23679