[ 
https://issues.apache.org/jira/browse/FLINK-26248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17494573#comment-17494573
 ] 

zhisheng edited comment on FLINK-26248 at 2/18/22, 12:28 PM:
-------------------------------------------------------------

thanks [~wangyang0918] quickly response, sorry , i just find that i not set the 
high-availability=zookeeper in flink-conf.yaml file. 

 

i found if i set ha, the job id is 00000000000000000000000000000000, and all 
the job checkpoint file will in the 
/flink/checkpoints/00000000000000000000000000000000/  folder , the job 
checkpoint and restart will it be affected? what should i do to slove this 
problem?


was (Author: zhisheng):
thanks [~wangyang0918] quickly response, sorry , i just find that i not set the 
high-availability=zookeeper in flink-conf.yaml file. 

 

i found if i set ha, the job id is 00000000000000000000000000000000, and all 
the job checkpoint file will in the 
/flink/checkpoints/00000000000000000000000000000000/  folder , the job 
checkpoint and restart will affect, what should i do to slove this problem?

> 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)

Reply via email to