[
https://issues.apache.org/jira/browse/SOLR-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12622906#action_12622906
]
Yonik Seeley commented on SOLR-683:
-----------------------------------
bq. The connection is only accepted if there's a thread to handle it.
Yes, but not from the normal pool... it looks like there are acceptor threads
that do nothing but accept socket connections.
I just confirmed that setting the acceptQueueSize does not work to reject
connections.
I put in a configurable sleep in the search handler and made requests until
they started blocking. Requests were still accepted and just hung... netstat
showed them to be "ESTABLISHED".
Further, setting a really low acceptQueueSize runs the risk of having
connections rejected even in a low-load situation because jetty doesn't accept
them fast enough.
> 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.
