[
https://issues.apache.org/jira/browse/SOLR-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12606428#action_12606428
]
Sean Timm commented on SOLR-502:
--------------------------------
The timeout is to protect the server side. The client side can be largely
protected by setting a read timeout, but if the client aborts before the server
responds, the server is just wasting resources processing a request that will
never be used. The partial results is useful in a couple of scenarios,
probably the most important is a large distributed complex where you would
rather get whatever results you can from a slow shard rather than throw them
away.
As a real world example, the query "contact us about our site" on a 2.3MM
document index (partial Dmoz crawl) takes several seconds to complete, while
the mean response time is sub 50 ms. We've had cases where a bot walks the
next page links (including expensive queries such as this). Also users are
prone to repeatedly click the query button if they get impatient on a slow
site. Without a server side timeout, this is a real issue.
Rate limiting and limiting the number of next pages that can be fetched at the
front end are also part of the solution to the above example.
> 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: Otis Gospodnetic
> Priority: Minor
> Fix For: 1.3
>
> Attachments: 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.
