user to the correct replica if
possible.
Thanks,
Markus
-Original message-
> From:Mark Miller
> Sent: Thu 24-Jan-2013 00:33
> To: solr-user@lucene.apache.org
> Subject: Re: Issues with docFreq/docCount on SolrCloud
>
>
> On Jan 23, 2013, at 6:21 PM, Yonik Seeley
On Jan 23, 2013, at 6:21 PM, Yonik Seeley wrote:
> A solr request could request a token that when resubmitted with a
> follow-up request would result in hitting the same replicas if
> possible.
Yeah, this would be good. It's also useful for not catching "eventual
consistency" effects between q
On Wed, Jan 23, 2013 at 6:15 PM, Markus Jelsma
wrote:
> We need, and i think many SolrCloud users are going to need this as well, to
> make replica's don't deviate too much from eachother, because if they do
> documents are certainly going to jump positions.
The synchronization that would be ne
ny thanks for sharing your thoughts,
Markus
-Original message-
> From:Michael Ryan
> Sent: Wed 23-Jan-2013 23:50
> To: solr-user@lucene.apache.org
> Subject: RE: Issues with docFreq/docCount on SolrCloud
>
> Are you able to see any evidence that some of the 500k docs ar
5:38 PM
To: solr-user@lucene.apache.org
Subject: RE: Issues with docFreq/docCount on SolrCloud
Hi again,
I've tried various settings for TieredMergePolicy to make sure the docFreq,
maxDoc and docCount don't deviate too much. We've also did tests after
increasing reclaimDeletesW
ard handler but i'm not sure this is a proper
solution. This, at least, might prevent users from seeing documents jumping
positions in the same result set.
Thanks,
Markus
-Original message-
> From:Markus Jelsma
> Sent: Mon 21-Jan-2013 20:31
> To: solr-user@lucene.apache.org
&
Hi,
We have a few trunk clusters running with two replica's for each shard. We
sometimes see results jumping positions for identical queries. We've tracked it
down to differences in docFreq and docCount between the leader and replica's.
The only way to force all cores in the shard to be consist
