solr-user [solr-u...@hotmail.com] wrote: > while we have optimized our queries for an average 50ms response time, > we do occasionally see some that can run between 10 and 100 seconds.
That sounds suspicious. Response times so far from your average indicates that there is special processing going on, such as uninverting facet fields after an index update or garbage collection with a very large heap. In both of these cases, termination (if it were possible) would be undesirable as those jobs needs to be done. > I know that this version of Solr itself doesn't have a built in timeout > mechanism, which leaves me with figuring out what to do (it seems to me that > I have to figure out how to get Tomcat to timeout the queries somehow) You can get tomcat to timeout, but it only breaks the connection with the client: The request is still processed in Solr and will end with an error entry in the log as it cannot deliver the result back to the client. Even if you were able to somehow kill the started thread from the outside, which Java does not support, it might leave the Solr structures in a problematic state: The only technically sane way to do time-based termination of a request is to build it into the application, i.e. Solr. - Toke Eskildsen
