[
https://issues.apache.org/jira/browse/SOLR-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12622706#action_12622706
]
Otis Gospodnetic commented on SOLR-683:
---------------------------------------
Hm, hard to tell from sparse Jetty javadocs.
http://docs.codehaus.org/display/JETTY/Configuring+Connectors states:
acceptQueueSize Number of connection requests that can be queued up
before the operating system starts to send rejections.
Sounds more like the latter than the former. That is, it sounds like Jetty
itself might accept connections until the OS starts complaining. Hm, either
way this doesn't help if one has an actual deadlock, like the one you described
in the 1-thread-example, does it?
> 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, SOLR-683.patch
>
>
> 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.
