lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Novin Novin <>
Subject Re: Always use leader for searching queries
Date Tue, 02 Jan 2018 17:33:02 GMT
Hi Erick,

You are right, it is XY Problem.

Allow me to explain best I can, I have two replica of one collection called
"Main". When I was using search feature in my application I get two
different numFound count. So I start digging after spending 2 3 hours I
found the one replica has numFound count higher than other (higher count
was not leader). I am not sure how It got end up like that. This count
difference affects paging on my application side not solr side.

Extra info might be useful to know
Same query not a single letter difference.
auto soft commit 20000
soft commit 60000
indexing data every minute.

Let me know if you need to know anything else. Any help would highly

Thanks in advance,

On Tue, 2 Jan 2018 at 15:14 Erick Erickson <> wrote:

> This seems like an XY problem. You're asking how to do X
> because you think it will solve problem Y without telling
> us what Y is.
> I say this because on the surface this seems to defeat the
> purpose behind SolrCloud. Why would you want to only make
> use of one piece of hardware? That will limit your throughput,
> so why bother to have replicas in the first place?
> Or is this some kind of diagnostic you're trying to implement?
> Best,
> Erick
> On Tue, Jan 2, 2018 at 5:08 AM, Novin Novin <> wrote:
> > Hi guys,
> >
> > I am using solr 5.5.4 and same version for solrj. My question is there
> any
> > way I can tell cloud solr client to use only leader for queries.
> >
> > Thanks in advance.
> > Navin

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message