[
https://issues.apache.org/jira/browse/SOLR-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12623247#action_12623247
]
Lars Kotthoff commented on SOLR-683:
------------------------------------
Yonik, you're right -- there're separate acceptor threads, setting
acceptQueueSize just affects how connections are handled when they come in too
quickly to be accepted by the available acceptor threads. There's no option to
influence handling connections when no executor threads are available. I've
verified that Tomcat behaves in the same way.
So the only thing we can do is up the thread count. Even setting timeouts won't
help as this only affects the actual network transfers, not the execution time
of the executor threads.
> 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.
