Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Implemented
-
1.19.0, 1.18.1
-
None
-
None
Description
FLINK-34007 revealed that we could use the ReleaseOnCall configuration parameter in Flink's KubernetesLeaderElector. Currently, we have to call `release` explicitly. This is due to a "bug" in v6.6.2 which only calls release or calls the notLeader callback. This was fixed in 0f6c6965 which ended up in v6.9.0.
This issue is about the following things:
- Upgrading the client
- Enabling ReleaseOnCall
- Remove explict #release call KubernetesLeaderElector#stopLeaderElectionCycle
Attachments
Issue Links
- is caused by
-
FLINK-34007 Flink Job stuck in suspend state after losing leadership in HA Mode
- Resolved