[FLINK-32422] EmbeddedLeaderService doesn't handle the leader events properly in edge cases

• Type: Sub-task
• Status: In Progress
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 1.18.0
• Component/s: Runtime / Coordination
• Labels: pull-request-available stale-assigned
• Assignee: Matthias Pohl
• Reporter: Matthias Pohl
• Created: 23/Jun/23 16:18
• Updated: 10/Aug/23 22:35

Description

The leadership is granted when registering the first contender. This sets the leadership flag within the EmbeddedLeaderService (see EmbeddedLeaderService:312ff: the grantLeadershipCall is triggered afterwards informing the contender about its leadership). In the meantime, close can be called on the contender which deregisters the contender again calling revoke on the contender without having been able to gain the leadership.

This issue was introduced by FLINK-30765.

Issue Links

• is caused by: FLINK-30765 LeaderElectionService.stop should always call revokeLeadership
• links to: GitHub Pull Request #22895
• mentioned in: Page Loading...