[FLINK-7655] Revisit default non-leader id for FencedRpcEndpoints

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.4.0
• Fix Version/s: 1.4.0
• Component/s: Runtime / Coordination
• Labels: flip-6
• Assignee: Till Rohrmann
• Reporter: Till Rohrmann
• Created: 20/Sep/17 12:45
• Updated: 21/Sep/17 23:00
• Resolved: 21/Sep/17 23:00

Description

Currently, when a FencedRpcEndpoint loses leadership, we set its leader id to a random value. This can be problematic, even though it's unlikely, because we might set it to a value which is used somewhere else (e.g. the currently valid leader id). I think it would be better to simply set the leader id to null in order to properly encode that the FencedRpcEndpoint is no longer a leader.

Issue Links

• links to: GitHub Pull Request #4689