Hi Team, While running the job in application mode...
# troubleshooting
c
Hi Team, While running the job in application mode in k8s cluster, I m facing an issue that last saved checkpoint is getting restored every time whenever I delete & create a new flink cluster. Ideally when I am taking a savepoint & starting. the cluster w/o providing any savepoint config details, then how come it restores the last saved checkpoint?
g
Are you using the Flink Kubernetes Operator?
if not, you are likely hitting a problem where you delete your cluster but the HA metadata is kept. In that case I suggest checking the operator which is designed to solve these requirements in a very nice and robust way
馃憦 1
c
thanks for pointing out the issue, using k8s operator is nt an option fr us, can you let me knw what needs to be done to solve this HA metadata problem?
g
you can look at how the operator implements stateful job upgrades
a
Sure, If you have some references or any document which we could refer for this, It would be very helpful for us.
Finding a way to use the operator will be much easier
you will save countless hours of sweat
and end up with a much more robust solution
a
Also, one more thing, whenever we restart the job, it tries to save checkpointing data to a file and throws the following error:
Copy code
Target file file:/opt/flink/pm/checkpoint/000000006e6b13320000000000000000/chk-1/_metadata already exists.
Is this also related to the above HA metadata issue
Sure, will see if we could use operator. Thanks