[
https://issues.apache.org/jira/browse/FLINK-6755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16846534#comment-16846534
]
Gyula Fora commented on FLINK-6755:
-----------------------------------
I agree with [~yanghua] that we should try to be consistent with the different
actions when it comes to the schedule. If the manual savepoint doesnt affect
the checkpointing schedule the manual checkpoint probably shouldnt either.
We can refactor the checkpointcoordinator but I see this as quite a small
change. Probably some extra property to the CheckpointProperties saying that
its user triggered so the regular checks like max concurrent checkpoints,
minimum time between, etc are not enforced.
> 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)
