Thank you Yang for your inputs...!
As a workaround I am doing the same by clearing up its state from ZK.
I am also evaluating alternatives for this by removing ZK based HA. As our
application is already in k8s, and pods are resilient. Also, AFAIK, flink
does not support active-active HA. So it wo
This might be related with FLINK-21928 and seems already fixed in 1.14.0.
But it will have some limitations and users need to manually clean up the
HA entries.
Best,
Yang
Parag Somani 于2022年2月24日周四 13:42写道：
> Hello,
>
> Recently due to log4j vulnerabilities, we have upgraded to Apache Flink
>
Hello,
Recently due to log4j vulnerabilities, we have upgraded to Apache Flink
1.14.3. What we observed we are getting following exception, and because of
it pod gets in crashloopback. We have seen this issues esp. during the time
of upgrade or deployment time when existing pod is already running.
