This log means the Flink internal leader elector failed to renew the leader
ConfigMap to keep its leadership. It might be caused by a network issue,
long fullGC or the K8s APIServer internal error.
This blog[1] could help you to know how the Kubernetes HA works.
[1]. https://flink.apache.org/2021
Hello everyone,
I am deploying a flink application cluster using k8S HA .
I notice this message in the log
@timestamp":"2022-03-21T17:11:39.436+01:00","@version":"1","message":"Renew
deadline reached after 200 seconds while renewing lock ConfigMapLock:
flink-pushavoo-flink-rec -
elifibre-000
