>From time to time I see massive number of threads that have commitScheduler in
>the name of the thread. When this happens, solr is pegging the disk IO and
>querying becomes unusable for a while. I have many collections (240 shards).
>It happens once in a while, I'm really not sure what is ca
lieve it's needed. I was hoping it
would help with performance related to time filtering and sorting. But, now it
seems to be performing quite well without it.
Tony
From: Schwartz, Tony
Sent: Friday, August 7, 2020 6:27 PM
To: solr-user@lucene.apache.org
Subject: RE: solr startup
sugges
being built on startup. Without them
they just come up in a second or so
> On Aug 7, 2020, at 6:03 PM, Schwartz, Tony wrote:
>
> I have many collections. When I start solr, it takes 30 - 45 minutes to
> start up and load all the collections. My collections are named per day.
>
I have many collections. When I start solr, it takes 30 - 45 minutes to start
up and load all the collections. My collections are named per day. During
startup, solr loads the collections in alpha-numeric name order. I would like
solr to load the collections in the descending order. So the
