[
https://issues.apache.org/jira/browse/FLINK-17487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17107341#comment-17107341
]
nobleyd commented on FLINK-17487:
---------------------------------
[~rmetzger] No, if I cancel the job, the checkpoints will be retained as the
document said. But, if I 'stop' the job and generate a savepoint, then the
checkpoint is cleared. While sometimes, the savepoint is not generated
successfully, and the job failed due to the 'stop' command, then I can not find
any more checkpoints. Besides, sometimes I stop the job and generate a
savepoint, but what I want to do is to restart the job with an early
checkpoint, but there won't be any early checkpoints.
> Do not delete old checkpoints when stop the job.
> ------------------------------------------------
>
> Key: FLINK-17487
> URL: https://issues.apache.org/jira/browse/FLINK-17487
> Project: Flink
> Issue Type: Improvement
> Components: Client / Job Submission, Runtime / Checkpointing
> Reporter: nobleyd
> Priority: Major
>
> When stop flink job using 'flink stop jobId', the checkpoints data is
> deleted.
> When the stop action is not succeed or failed because of some unknown errors,
> sometimes the job resumes using the latest checkpoint, while sometimes it
> just fails, and the checkpoints data is gone.
> You may say why I need these checkpoints since I stop the job and a savepoint
> will be generated. For example, my job uses a kafka source, while the kafka
> missed some data, and I want to stop the job and resume it using an old
> checkpoint. Anyway, I mean sometimes the action stop is failed and the
> checkpoint data is also deleted, which is not good.
> This feature is different from the case 'flink cancel jobId' or 'flink
> savepoint jobId', which won't delete the checkpoint data.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
