I've tried both timeAllowed and cpuAllowed and neither are restricting the amount of time the queries take to run. I have a test query that's reliably taking 20-30 seconds, if there's any useful debug params or such I can run to provide the information you want I'm happy to run them - I'm not sure how to usefully interrogate solr for where its time is being spent, sorry
Thanks On Wed, 6 Nov 2024 at 14:25, Gus Heck <gus.h...@gmail.com> wrote: > There are unit tests that seem to suggest that timeAllowed still works, can > you provide some more information about your use case? Particularly > important is any information about where (what code) your queries are > spending a lot of time in if you have it. > > On Wed, Nov 6, 2024 at 6:18 AM Dominic Humphries > <domi...@adzuna.com.invalid> > wrote: > > > 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 > > > > > -- > http://www.needhamsoftware.com (work) > https://a.co/d/b2sZLD9 (my fantasy fiction book) >
