[ 
https://issues.apache.org/jira/browse/FLINK-6755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16857225#comment-16857225
 ] 

vinoyang commented on FLINK-6755:
---------------------------------

[~klion26] The considerations facing this issue also exist in your FLINK-12619, 
if you read the comments again. In fact, stop-with-checkpoint is just one of 
the special cases of triggering checkpoints manually. This is why I ping you 
and [~aljoscha]. Of course, I agree with your worry about "vulnerabilities", 
but this also exists in savepoint.

I agree with [~gyfora] 's point of view, I think we need to seriously consider 
the needs that users really care about. If this feature is truly valuable to 
users, we don't have to wait for a long release cycle. Of course, I am not 
saying that the problems facing the moment are not important, but they are 
already there, and we can also push it together to see how to solve them.

> 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)

Reply via email to