[
https://issues.apache.org/jira/browse/FLINK-26248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhisheng updated FLINK-26248:
-----------------------------
Description:
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
was:
flink version: 1.12.0
ha: zk
mode: application mode
native k8s
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
> 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
>
> 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)
