You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "vinoyang (JIRA)" <ji...@apache.org> on 2019/05/13 07:30:01 UTC
[jira] [Comment Edited] (FLINK-6755) Allow triggering Checkpoints
through command line client
[ https://issues.apache.org/jira/browse/FLINK-6755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16838322#comment-16838322 ]
vinoyang edited comment on FLINK-6755 at 5/13/19 7:29 AM:
----------------------------------------------------------
I think trigger checkpoints manually is a very valuable feature to users. I'd like to implement this feature. But it has been created so long time and did not receive feedback. Is there anything obstacle exists? [~gyfora] [~richtesn] [~till.rohrmann]
was (Author: yanghua):
I think trigger checkpoints manually is a very valuable feature for users. I'd like to implement this feature. But it has been created so long time and did not receive feedback. Is there anything obstacle exists? [~gyfora] [~richtesn] [~till.rohrmann]
> 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
> Assignee: vinoyang
> Priority: Major
>
> 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
(v7.6.3#76005)