[
https://issues.apache.org/jira/browse/FLINK-6755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16856860#comment-16856860
]
Congxian Qiu(klion26) commented on FLINK-6755:
----------------------------------------------
The two issues are indeed related, but the solutions proposed are totally
different from my point of view.
FLINK-12619 stems from the idea of FLINK-11458 (stop job with savepoint), the
management of checkpoint is still controlled by framework and user could only
*ask* the framework to perform *one single* checkpoint *at end of the job*,
instead of at any time w/o limit.
However, just like [~till.rohrmann] and [~srichter] mentioned, the proposal
here leaks the management of checkpoint to users and may introduce side effects
or even vulnerabilities (one could trigger unlimited checkpoints with unlimited
interval if only get the job id and access to cluster).
> 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)