[SOLR-3939] An empty or just replicated index cannot become the leader of a shard after a leader goes down.

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 4.0-BETA, 4.0
• Fix Version/s: 4.1, 6.0
• Component/s: SolrCloud
• Labels: 4.0.1_Candidate
• Assignee: Mark Miller
• Reporter: Joel Bernstein
• Created: 12/Oct/12 14:13
• Updated: 09/May/16 18:58
• Resolved: 26/Oct/12 15:31

Description

When a leader core is unloaded using the core admin api, the followers in the shard go into recovery but do not come out. Leader election doesn't take place and the shard goes down.

This effects the ability to move a micro-shard from one Solr instance to another Solr instance.

The problem does not occur 100% of the time but a large % of the time.

To setup a test, startup Solr Cloud with a single shard. Add cores to that shard as replicas using core admin. Then unload the leader core using core admin.

Issue Links

• relates to: SOLR-3940 Rejoining the leader election incorrectly triggers the code path for a fresh cluster start rather than fail over.