Skimming this thread, I don't see any mention of what seems like the most likely culprit to me:
Solr 9.3's refactoring of the timeAllowed functionality hamstrung *MOST* of the code paths that timeAllowed is realy useful for (spellcheck, facets, synonym expansion, etc...) by disabling ExitableDirectoryReader by default. https://issues.apache.org/jira/browse/SOLR-16693 https://solr.apache.org/guide/solr/latest/upgrade-notes/major-changes-in-solr-9.html#use-of-timeallowed Some work has been done to try and imporve the default behavior of Solr when QueryLimits (the generalization of timeAllowed) are in use -- but IMO until SOLR-17182 is done, anyone trying to use timeAllowed *MUST* set `-Dsolr.useExitableDirectoryReader=true` when running their solr nodes, or setting timeAllowed=123 on your requests is basically just a waste of 16 bytes every request. : Date: Wed, 6 Nov 2024 11:17:58 +0000 : From: Dominic Humphries <domi...@adzuna.com.invalid> : Reply-To: users@solr.apache.org : To: users@solr.apache.org : Subject: timeAllowed in Solr 9 : : Hi folks, : : we're testing Solr 9.7 to upgrade our existing 8.11 stack. We're seeing a : problem with long requests: we send `timeAllowed=4900` which works fine on : the existing 8.11 and keeps requests to just a few seconds. : : With 9.7, however, the flag is basically ignored - requests can take over : 30 seconds whether the flag is present or not, which is causing higher CPU : load and slowing response times. : : I've tried setting the flag suggested in : https://solr.apache.org/guide/solr/latest/upgrade-notes/major-changes-in-solr-9.html#use-of-timeallowed : - but even with solr.useExitableDirectoryReader set we still don't get the : desired behaviour. : : Is there anything else I can try to get the old behaviour back? : : Thanks : -Hoss http://www.lucidworks.com/
