[
https://issues.apache.org/jira/browse/SOLR-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621616#action_12621616
]
Yonik Seeley commented on SOLR-683:
-----------------------------------
bq. So this seems to be a container level issue, not a Solr issue?
Yes and no... it's not a low-level solr bug, and it can be solved by upping the
number of concurrent threads or http requests in the container.
But if we could set a read timeout on shard requests, we could also prevent a
hard deadlock and return an error instead. In any case, we should increase the
number of threads in the example jetty config and document this issue.
> 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.
