On 8/5/22 14:21, Surya R wrote:
When the solr dameon is restarted, the cores do appear on the admin
console, but when a query is hit against the core immediately, We dont get
a response, it spins for like 20 seconds and then only after i see the
below message in the log, i get the results. Why is it taking longer in
solr 8.x to server the queries after a restart of solr
I would be interested in seeing the entire solr.log file from server
start to successful slow query, to see if there's anything in there that
can say what Solr is doing during that time.
Here is an answer to an almost identical question that covers things I
wouldn't have thought of:
https://stackoverflow.com/questions/68709357/why-first-occurrence-of-a-query-takes-more-time-than-the-following-on-solrcloud
Are you in SolrCloud mode? If so, is there more than one Solr node in
the cluster? What are the sizes of those 8 cores? Both on-disk size
and document counts, deleted and max. What are the total memory and
process memory characteristics of the server? Getting a screenshot of
the processes as described at the following URL could be helpful:
https://cwiki.apache.org/confluence/display/solr/solrperformanceproblems#SolrPerformanceProblems-Askingforhelponamemory/performanceissue
Note that the mailing list eats almost all attachments, so you can't
attach the screenshot to an email. You'll need to put it on a file
sharing site and send us a URL to access it.
Usually upgrading two major versions yields better performance, not
worse. We need more information to provide an answer.
Thanks,
Shawn
