[ https://issues.apache.org/jira/browse/FLINK-6755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16846506#comment-16846506 ]
vinoyang edited comment on FLINK-6755 at 5/23/19 7:23 AM: ---------------------------------------------------------- [~srichter] [~gyfora] What do you think about the proposal that I suggest the manually trigger checkpoint does not use the timer to schedule? IMO, I think we should introduce a bit of abstract about the trigger strategy. was (Author: yanghua): [~srichter] [~gyfora] What do you think about the proposal that I suggest the manually trigger checkpoint does not use the timer to schedule? > 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)