You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Piotr Nowojski (Jira)" <ji...@apache.org> on 2022/04/14 11:20:00 UTC

[jira] [Reopened] (FLINK-6755) Allow triggering Checkpoints through command line client

     [ https://issues.apache.org/jira/browse/FLINK-6755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Piotr Nowojski reopened FLINK-6755:
-----------------------------------

> Allow triggering Checkpoints through command line client
> --------------------------------------------------------
>
>                 Key: FLINK-6755
>                 URL: https://issues.apache.org/jira/browse/FLINK-6755
>             Project: Flink
>          Issue Type: New Feature
>          Components: Command Line Client, Runtime / Checkpointing
>    Affects Versions: 1.3.0
>            Reporter: Gyula Fora
>            Priority: Minor
>              Labels: auto-deprioritized-major, auto-unassigned
>
> 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.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)