[
https://issues.apache.org/jira/browse/SOLR-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12622245#action_12622245
]
Magne Groenhuis commented on SOLR-502:
--------------------------------------
I am using the trunk version of Solr and split a lucene index in 2 (2 GB)
shards hosting them on 2 different ports.
Even though i know work is being done outside the timeAllowed period, i get
some extreme numbers giving the user impression that timeAllowed is not
actually doing anything.
INFO: webapp=/solr path=/select
params={fl=bla1&shards=localhost:8983/solr,localhost:7574/solr&start=65850&q=bla2&timeAllowed=1000&wt=javabin&rows=5&version=2.2}
status=0 QTime=331390
I am browsing to the end of some search result. I assume that under the hood an
extreme amount of id's with scores have to be sent to the merge machine, but i
was hoping that the timeAllowed parameter would limit the amount of time
seacrhed on the shards and thus limiting the time for the client. Possible
resulting in getting no result (because of the browsing so far to the end of a
large search result).
But still the number 1000 and 331390 are a bit far apart.
Any suggestions or do i have to give some more data?
> Add search time out support
> ---------------------------
>
> Key: SOLR-502
> URL: https://issues.apache.org/jira/browse/SOLR-502
> Project: Solr
> Issue Type: New Feature
> Components: search
> Reporter: Sean Timm
> Assignee: Yonik Seeley
> Priority: Minor
> Fix For: 1.3
>
> Attachments: SOLR-502.patch, SOLR-502.patch, SOLR-502.patch,
> SOLR-502.patch, SOLR-502.patch, SOLR-502.patch, solrTimeout.patch,
> solrTimeout.patch, solrTimeout.patch, solrTimeout.patch, solrTimeout.patch
>
>
> Uses LUCENE-997 to add time out support to Solr.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
