[
https://issues.apache.org/jira/browse/FLINK-6755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458438#comment-17458438
]
Piotr Nowojski edited comment on FLINK-6755 at 4/15/22 12:51 PM:
-----------------------------------------------------------------
The motivation behind this feature request will be covered by FLINK-25276.
As mentioned above by Aljoscha, there might be still a value of exposing manual
checkpoint triggering REST API hook, so I'm keeping this ticket open. However
it doesn't look like such feature is well motivated. Implementation of this
should be quite straightforward since Flink internally already supports this
(FLINK-24280). It's just not exposed in anyway to the user.
edit: Although this idea might be still valid, I strongly think we should not
expose checkpoint directory when triggering checkpoints as proposed in the
description:
{noformat}
./bin/flink checkpoint <jobID> [checkpointDirectory]
{noformat}
Since checkpoints are owned fully by Flink, CLI/REST API call to trigger
checkpoints should not expose anything like that. If anything, it should be
just a simple trigger with optionally parameters like whether the checkpoint
should be full or incremental.
was (Author: pnowojski):
The motivation behind this feature request will be covered by FLINK-25276.
As mentioned above by Aljoscha, there might be still a value of exposing manual
checkpoint triggering REST API hook, so I'm keeping this ticket open. However
it doesn't look like such feature is well motivated. Implementation of this
should be quite straightforward since Flink internally already supports this
(FLINK-24280). It's just not exposed in anyway to the user.
> 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
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-unassigned
>
> 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
(v8.20.1#820001)
