[
https://issues.apache.org/jira/browse/SOLR-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved SOLR-683.
-------------------------------
Resolution: Fixed
The problem with a read timeout is it would cause otherwise perfectly
acceptable requests to fail, even if the system is not under load (since we
can't put an upper bound on how long a request can take).
I'm resolving this for now since I upped the max threads in the example
jetty.xml to 10K and documented the issue on the distributed search wiki page.
If the servlet container can be configured to reject requests rather than
blocking, that would probably be the ideal scenario. If anyone knows if Jetty
can be configured to do that, we can add it to the solr example.
> Distributed Search / Shards Deadlock
> ------------------------------------
>
> Key: SOLR-683
> URL: https://issues.apache.org/jira/browse/SOLR-683
> Project: Solr
> Issue Type: Bug
> Components: search
> Affects Versions: 1.3
> Environment: Linux
> jre1.6.0_05
> 8GB RAM
> 2 x 2 core AMD 2.4 Ghz
> 2 x 140GB disk
> Reporter: Cameron
> Assignee: Yonik Seeley
> Fix For: 1.3
>
> Attachments: locked.log
>
>
> Per this discussion:
> http://www.nabble.com/Distributed-Search-Strategy---Shards-td18882112.html
> Solr seems to lock up when running distributed search on three servers, with
> all three using shards of each other. Thread dump attached.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
