Steve Davids created SOLR-5986:
----------------------------------
Summary: When a query times out all distributed searches shouldn't
continue on until completion
Key: SOLR-5986
URL: https://issues.apache.org/jira/browse/SOLR-5986
Project: Solr
Issue Type: Improvement
Components: search
Reporter: Steve Davids
Priority: Critical
Fix For: 4.9
The intent of this ticket is to have all distributed search requests stop
wasting CPU cycles on requests that have already timed out. We have come across
a case where a nasty wildcard query within a proximity clause was causing the
cluster to enumerate terms for hours even though the query timeout was set to
minutes. This caused a noticeable slowdown within the system which made us
restart the replicas that happened to service that one request.
[~amccurry] Built a mechanism into Apache Blur to help with the issue in
BLUR-142 (see commit comment for code, though look at the latest code on the
trunk for newer bug fixes).
Ideally Solr will distribute the timeout request parameter and automatically
interrupt all query threads once the threshold is met. This issue mirrors what
others have discussed on the mailing list:
http://mail-archives.apache.org/mod_mbox/lucene-solr-user/200903.mbox/%[email protected]%3E
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
