[
https://issues.apache.org/jira/browse/FLINK-26248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17495922#comment-17495922
]
Yang Wang commented on FLINK-26248:
-----------------------------------
It depends on how you will restart your Flink job. If you want to recover the
Flink job from latest checkpoint, then the retained HA ConfigMap could help.
Otherwise, if you want a fresh start, you need to stop/cancel the Flink job
instead of deleting the JobManager deployment directly.
> flink job not recover from latest checkpoint on native k8s
> ----------------------------------------------------------
>
> Key: FLINK-26248
> URL: https://issues.apache.org/jira/browse/FLINK-26248
> Project: Flink
> Issue Type: Bug
> Components: Deployment / Kubernetes
> Affects Versions: 1.12.0
> Reporter: zhisheng
> Priority: Major
> Attachments: image-2022-02-22-10-26-53-699.png
>
>
> flink version: 1.12.0
> ha: zk
> mode: application mode
> native k8s
>
> 1、if flink job start with savepoint, running for a while，then i delete the JM
> pod, the job will restart with the old savepoint not the latest checkpoint.
> this is not what i want
> if i delete the TM pod, the job will restart with the latest the
> checkpoint，this is what i want
>
> 2、if start job without savepoint, running for a while，then i delete the JM
> pod, the job will restart from earliest not the latest checkpoint
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
