We wrote a script which queries each Solr instance in cloud
(http://$host/solr/replication?command=details) and subtracts the
‘replicableVersion’ number from the ‘indexVersion’ number, converts to minutes,
and alerts if the minutes exceed 20. We get alerted many times a day. The soft
commit setting is every 7 minutes.
Any idea what might be wrong here?
This is our commit setting.
<autoCommit>
<maxTime>15000</maxTime>
<maxDocs>100000</maxDocs>
<openSearcher>false</openSearcher>
</autoCommit>
<autoSoftCommit>
<maxTime>450000</maxTime>
</autoSoftCommit>
We got 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 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 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 with
> the documents till the nodes are in sync. I always use SolrJ which talks to
> Solr through zookeeper, even with that it seemed to be unavoidable at times.
> We are committing every 10 mins. I'm pretty much sure there's a minor glitch
> which creates a sync issue at times.
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/solr-query-gives-different-numFound-upon-refreshing-tp4155414p4157026.html
> Sent from the Solr - User mailing list archive at Nabble.com.
