I did not have a suggester set up.  I disabled the spell checker component, but 
that wasn't the problem.  I found my issue... it was related to a warming query 
i was running for each newly opened searcher.  Early on I enabled that, but I 
completely forgot about it.  And i don't believe 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

suggester?  what do i need to look for in the configs?

Tony



Sent from my Verizon, Samsung Galaxy smartphone



-------- Original message --------
From: Dave <hastings.recurs...@gmail.com<mailto:hastings.recurs...@gmail.com>>
Date: 8/7/20 18:23 (GMT-05:00)
To: solr-user@lucene.apache.org<mailto:solr-user@lucene.apache.org>
Subject: Re: solr startup

It sounds like you have suggester indexes 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 
> <tony.schwa...@cinbell.com<mailto:tony.schwa...@cinbell.com>> 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.  
> 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 most 
> recent collections are loaded first and are available for searching while the 
> older collections are not as important.  Is this possible?
>
>

Reply via email to