ello - your similarity should rely on numDoc instead, it solves the
> > problem. I believe it is already fixed in trunk, but i am not sure.
> > Markus
> >
> > -----Original message-----
> >> From:Upayavira
> >> Sent: Thursday 4th August 2016 13:59
>
ma
wrote:
> Hello - your similarity should rely on numDoc instead, it solves the problem.
> I believe it is already fixed in trunk, but i am not sure.
> Markus
>
> -Original message-
>> From:Upayavira
>> Sent: Thursday 4th August 2016 13:59
>> To: solr-user@l
Hello - your similarity should rely on numDoc instead, it solves the problem. I
believe it is already fixed in trunk, but i am not sure.
Markus
-Original message-
> From:Upayavira
> Sent: Thursday 4th August 2016 13:59
> To: solr-user@lucene.apache.org
> Subject: Out of sy
We have a system that has a reasonable number of changes going on on a
daily basis (maybe 60m docs, and around 1m updates per day). Using Solr
Cloud, the data is split into 10 shards and those shards are replicated.
What we are finding is that the number of deletions is causing differing
maxDocs a
