Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
MIME-Version: 1.0
From: Webster Homer <webster.homer@sial.com>
Date: Mon, 22 May 2017 15:41:57 -0500
Message-ID: <CAKTEqfkk6v5FtsyNaLxrWf8V=V0EXt9iHXYStuom=UoOj4w3tA@mail.gmail.com>
Subject: solrcloud replicas not in sync
To: solr-user@lucene.apache.org
Content-Type: multipart/alternative; boundary="001a114d4d72f62f29055022e6a1"
archived-at: Mon, 22 May 2017 20:42:04 -0000

--001a114d4d72f62f29055022e6a1
Content-Type: text/plain; charset="UTF-8"

I have a solrcloud collection with 2 shards and 4 replicas. The replicas
for shard 1 have different numbers of records, so different queries will
return different numbers of records.

I am not certain how this occurred, it happened in a collection that was a
cdcr target.

Is there a way to limit a search to a specific replica of a shard? We want
to understand the differences

Is there a way to recover when a shard has inconsistent replicas.
If I use the delete replica API call to delete one of them and then use add
replica to create it from scratch will it auto-populate from the other
replica in the shard?

Thanks,
Webster

-- 


This message and any attachment are confidential and may be privileged or 
otherwise protected from disclosure. If you are not the intended recipient, 
you must not copy this message or attachment or disclose the contents to 
any other person. If you have received this transmission in error, please 
notify the sender immediately and delete the message and any attachment 
from your system. Merck KGaA, Darmstadt, Germany and any of its 
subsidiaries do not accept liability for any omissions or errors in this 
message which may arise as a result of E-Mail-transmission or for damages 
resulting from any unauthorized changes of the content of this message and 
any attachment thereto. Merck KGaA, Darmstadt, Germany and any of its 
subsidiaries do not guarantee that this message is free of viruses and does 
not accept liability for any damages caused by any virus transmitted 
therewith.

Click http://www.emdgroup.com/disclaimer to access the German, French, 
Spanish and Portuguese versions of this disclaimer.

--001a114d4d72f62f29055022e6a1--