Unfortunately the timeAllowed parameter doesn't apply to the part of the processing that makes wildcard queries so slow. It only applies to a later part of the processing when the matching documents are being collected. There's some discussion in the original ticket that implemented this (https://issues.apache.org/jira/browse/SOLR-502). I'm not sure if there's a newer ticket for implementing an end-to-end timeout.
-Michael -----Original Message----- From: Mario-Leander Reimer [mailto:mario-leander.rei...@qaware.de] Sent: Thursday, March 27, 2014 12:15 PM To: solr-user@lucene.apache.org Subject: timeAllowed query parameter not working? Hi Solr users, currently I have some really long running user entered pure wildcards queries (like *??) , these are hogging the CPU for several minutes. So what I tried is setting the "timeAllowed" query parameter via the search handler in solrconfig.xml. But without any luck, the parameter does not seem tob e working. Here is my search handler definition: <requestHandler name="/select" class="solr.SearchHandler" default="true"> <lst name="defaults"> <int name="rows">10</int> <str name="df">TEXT</str> <int name="timeAllowed">10000</int> </lst> </requestHandler> Thanks for your help! Leander
