Hi All,
We running solrcloud 7.6 (with the patch #
https://issues.apache.org/jira/secure/attachment/12969150)/SOLR-11724.patchon
production on 7 hosts in containers. The container memory is 48GB , heap
is 24GB.
ulimit -v
unlimited
ulimit -m
unlimited
We don't have any custom code in solr. We
What that error usually means is that there are a zillion threads running.
Try taking a thread dump. It’s _probable_ that it’s CDCR, but
take a look at the thread dump to see if you have lots of
threads that are running. Any by “lots” here, I mean 100s of threads
that reference the same component,
I think my original post didn't go through because I wasn't subscribed so
apologizes if this is a duplicate.
For both Solr 7 and Solr 8, we have found that attempts to do range queries on
DatePointField when there are a large number of points performs poorly (queries
were taking over 30 seconds
As long as the data is loading you are fine I believe. We can create a
ticket to figure out that error, but it's not affecting the logic of the
load in any way.
Joel Bernstein
http://joelsolr.blogspot.com/
On Sun, Mar 29, 2020 at 2:29 AM Kayak28 wrote:
> Hello, Community:
>
> Thank you for re
Is CDCR even recommended to be used in production?
Or it was abandoned before it could become production ready ?
Thanks
SG
On Sun, Mar 29, 2020 at 5:18 AM Erick Erickson
wrote:
> What that error usually means is that there are a zillion threads running.
>
> Try taking a thread dump. It’s _prob
Is there any good way of having a load-balancer across two SolrCloud
clusters (version 8.x or 7.x) that are in different regions (like Azure
East and Azure West) ?
Thanks
SG
On Thu, Mar 26, 2020 at 4:53 AM Erick Erickson
wrote:
> I’ve never even heard of someone trying to put
> different ensemb
I don’t recommend CDCR at this point, I think there better approaches.
The root problem is that CDCR uses tlog files as a queueing mechanism.
If the connection between the DCs is broken for any reason, the tlogs grow
without limit. This could probably be fixed, but a better alternative is to
use s