Fabrizzio Chavez
03/18/2025, 10:04 AMs3.endpoint: http://my-minio.com:9000
s3.path.style.access: "true"
high-availability.type: kubernetes
high-availability.storageDir: "s3://flink-deployments/ha"
state.savepoints.dir: "s3://flink-deployments/savepoints"
state.checkpoints.dir: "s3://flink-deployments/checkpoints"
So after upgrade the service, restart it using restartNonce flag, or killing the job manager or task manager pods the service recognizes the last jobId and continues working.
But, the only problem that I found is when I am recreating the flinkDeployment, in this case it creates a new jobId and ignores the previous checkpoints or ha metadata stored in s3, why happens that? is this an expected behaviour in case of deletion and recreation of flinkDeployments? I verified that the kubernetes.cluster-id is exactly the same before the deletion. I would like to guarantee that in case of redeployments, the same jobId should be re attached to the new flinkDeployment instancePedro Mázala
03/18/2025, 10:20 AMflink-deployment:
...
job:
initialSavepointPath: ...
Where you can define from which savepoint/checkpoint your job should start from.
When you use the k8s operator, it should make the trick automatically for youFabrizzio Chavez
03/18/2025, 2:44 PMPedro Mázala
03/18/2025, 2:48 PMFabrizzio Chavez
03/18/2025, 2:49 PMPedro Mázala
03/18/2025, 2:50 PMjob.upgradeMode ?Fabrizzio Chavez
03/18/2025, 2:54 PMPedro Mázala
03/18/2025, 2:55 PMFabrizzio Chavez
03/18/2025, 2:59 PMFabrizzio Chavez
03/18/2025, 3:00 PMPedro Mázala
03/18/2025, 3:08 PMjob.initialSavepointPath on each deployment I'm afraidFabrizzio Chavez
03/18/2025, 4:52 PMPedro Mázala
03/19/2025, 10:25 AM