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/02/10/native-k8s-with-ha.html Best, Yang marco andreas <[email protected]> 于2022年3月22日周二 03:41写道： > 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-00000000000000000000000000000000-jobmanager-leader > (58de99f0-67dd-4a5c-9850-b26f9cb8e759)","logger_name":"io.fabric8.kubernetes.client.extended.leaderelection.LeaderElector","thread_name":"pool-100902-thread-1","level":"DEBUG","level_value":10000 > > > Can anyone explain what is the cause of this and how to prevent it,By the > way, any useful documentation about the flink HA feature on k8S would be > appreciated. > > flink version : 1.13.5 > > Thanks, > >
