Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
1.18.0
Description
The current implementations of LeaderElectionService do not implement the stop() call consistently. Some (e.g. StandaloneLeaderElectionService call revoke on the LeaderContender) whereas others don't (e.g. DefaultLeaderElectionService). The MultipleComponentLeaderElectionService does call revoke on the LeaderContender instances, though.
We should align this behavior and specify it in the LeaderElectionService contract before going ahead with refactoring the interfaces (FLIP-285).
Attachments
Issue Links
- causes
-
FLINK-32422 EmbeddedLeaderService doesn't handle the leader events properly in edge cases
- In Progress
- is duplicated by
-
FLINK-30763 Make TestingLeaderElectionService comply to how the LeaderElectionService interface is intended
- Closed
- is related to
-
FLINK-30759 Merge DispatcherRunnerLeaderElectionLifecycleManager into DefaultDispatcherRunner
- Resolved
-
FLINK-19542 Implement LeaderElectionService and LeaderRetrievalService based on Kubernetes API
- Closed
- links to