[
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 stale-minor (was:
auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: Minor
> Labels: auto-deprioritized-major, stale-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.3.4#803005)
