rid of all max new searcher errors.
-Original Message-
From: Erick Erickson [mailto:erickerick...@gmail.com]
Sent: Thursday, September 04, 2014 6:07 PM
To: solr-user@lucene.apache.org
Subject: Re: solr query gives different numFound upon refreshing
Does this persist if you issue a hard
I've noticed similar behavior with our Solr cloud cluster for a while, it's
random though. We've 2 shards with 3 replicas each. At times, I've observed
that the same query on refresh will fetch different results (numFound) as
well as the content. The only way to mitigate is to refresh the index
Does this persist if you issue a hard commit? You can do something like
http://solr/collection/update?stream.body=commit/
On Thu, Sep 4, 2014 at 2:19 PM, shamik sham...@gmail.com wrote:
I've noticed similar behavior with our Solr cloud cluster for a while, it's
random though. We've 2 shards
registeredAt: 2014-08-28T16:21:02.278Z
warmupTime: 65727
Thanks for all help.
-Original Message-
From: Shawn Heisey [mailto:s...@elyograg.org]
Sent: Wednesday, August 27, 2014 2:37 PM
To: solr-user@lucene.apache.org
Subject: Re: solr query gives different numFound upon refreshing
(Searching)
What is Master Searching vs. Master Replicable vs Slave Searching?
Thanks.
-Original Message-
From: Erick Erickson [mailto:erickerick...@gmail.com]
Sent: Friday, August 29, 2014 12:22 AM
To: solr-user@lucene.apache.org
Subject: Re: solr query gives different numFound upon
@lucene.apache.org
Subject: Re: solr query gives different numFound upon refreshing
On 8/27/2014 10:44 AM, Bryan Bende wrote:
Theoretically this shouldn't happen, but is it possible that the two
replicas for a given shard are not fully in sync?
Say shard1 replica1 is missing a document that is in shard1
-28T16:21:02.278Z
warmupTime: 65727
Thanks for all help.
-Original Message-
From: Shawn Heisey [mailto:s...@elyograg.org]
Sent: Wednesday, August 27, 2014 2:37 PM
To: solr-user@lucene.apache.org
Subject: Re: solr query gives different numFound upon refreshing
On 8/27/2014 10
Theoretically this shouldn't happen, but is it possible that the two
replicas for a given shard are not fully in sync?
Say shard1 replica1 is missing a document that is in shard1 replica2... if
you run a query that would hit on that document and run it a bunch of
times, sometimes replica 1 will
On 8/27/2014 10:44 AM, Bryan Bende wrote:
Theoretically this shouldn't happen, but is it possible that the two
replicas for a given shard are not fully in sync?
Say shard1 replica1 is missing a document that is in shard1 replica2... if
you run a query that would hit on that document and run
