lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jack Krupansky" <>
Subject Re: how are you handling killer queries?
Date Mon, 03 Jun 2013 14:59:45 GMT
There are two radically distinct use cases:

1. Consumers on the open Internet. They do stupid things. Give them a very 
constrained search experience, enforced with query preprocessing. Maybe give 
them only dismax queries.
2. Professional power users. They typically have "credentials" for using the 
application, so if they are detected as performing long or stupid queries, 
log the details and administratively take action, such as denying them 
access (or billing them for excessive resource usage.)

-- Jack Krupansky

-----Original Message----- 
From: Bernd Fehling
Sent: Monday, June 03, 2013 4:39 AM
Subject: how are you handling killer queries?

How are you handling "killer queries" with solr?

While solr/lucene (currently 4.2.1) is trying to do its best I see sometimes 
stupid queries
in my logs, located with extremly long query time.


I even get hits for this (hits=34091309 status=0 QTime=88667).

But the jetty log says:
WARN:oejs.Response:Committed before 500 {msg=Daten├╝bergabe unterbrochen
(broken pipe),
35 more|,code=500}
java.lang.IllegalStateException: Committed
        at org.eclipse.jetty.server.Response.resetBuffer(

Because I get hits and qtime the search is successful, right?

But jetty/http has already closed the connection and solr doesn't know about 

How are you handling "killer queries", just ignoring?
Or something to tune (jetty config about timeout) or filter (query 

Would be pleased to hear your comments.


View raw message