[
https://issues.apache.org/jira/browse/FLINK-17487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-17487:
-----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor (was:
auto-deprioritized-major stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> 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: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> 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.20.1#820001)
