You are viewing a plain text version of this content. The canonical link for it is here.

Posted to solr-dev@lucene.apache.org by "Yonik Seeley (JIRA)" <ji...@apache.org> on 2007/02/03 00:23:05 UTC

[jira] Commented: (SOLR-138) queries can stack up

    [ https://issues.apache.org/jira/browse/SOLR-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469905 ] 

Yonik Seeley commented on SOLR-138:
-----------------------------------

One method to "fix" this would be to limit the number of queries that may be executing at any one time (queueing).
http://www.nabble.com/TermInfosReader-lazy-term-index-reading-tf3162657.html#a8776274

One could do this in the servlet container by limiting the number of threads in the thread pool, but would that lock out the admin pages?

A more flexible way might be to put the queueing in the SolrCore.exec() method.
Admin pages could bypass the exec() method by calling a handler directly, or could set a priority on the request that avoided queueing.


> queries can stack up
> --------------------
>
>                 Key: SOLR-138
>                 URL: https://issues.apache.org/jira/browse/SOLR-138
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Yonik Seeley
>
> A burst of "expensive" queries can cause contention within lucene, greatly reducing effective throughput and causing more and more queries to stack up.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.