[SOLR-8173] CLONE - Leader recovery process can select the wrong leader if all replicas for a shard are down and trying to recover as well as lose updates that should have been recovered.

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Duplicate
• Component/s: SolrCloud
• Labels: leader recovery
• Assignee: Mark Miller
• Reporter: Matteo Grolla
• Created: 20/Oct/15 16:23
• Updated: 28/Feb/18 00:09
• Resolved: 28/Feb/18 00:09

Description

I'm doing this test
collection test is replicated on two solr nodes running on 8983, 8984
using external zk
initially both nodes are empty

1)turn on solr 8983
2)add,commit a doc x con solr 8983
3)turn off solr 8983
4)turn on solr 8984
5)shortly after (leader still not elected) turn on solr 8983
6)8984 is elected as leader
7)doc x is present on 8983 but not on 8984 (check issuing a query)

In attachment are the solr.log files of both instances

Issue Links

• is a clone of: SOLR-5552 Leader recovery process can select the wrong leader if all replicas for a shard are down and trying to recover as well as lose updates that should have been recovered.
• is duplicated by: SOLR-12011 Consistence problem when in-sync replicas are DOWN