[SOLR-3940] Rejoining the leader election incorrectly triggers the code path for a fresh cluster start rather than fail over.

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 4.1, 6.0
• Component/s: SolrCloud
• Labels: 4.0.1_Candidate
• Assignee: Mark Miller
• Reporter: Mark Miller
• Created: 12/Oct/12 15:59
• Updated: 09/May/16 18:58
• Resolved: 12/Oct/12 20:05

Description

A rejoin may happen when a node decides it may not be the best leader candidate.

This means that in certain fail over situations, the new leader election may wait until a timeout expires before proceeding - instead, there should be no wait because the we should not expect that the leader that went down is coming back anytime soon.

Issue Links

• is related to: SOLR-3939 An empty or just replicated index cannot become the leader of a shard after a leader goes down.