[ https://issues.apache.org/jira/browse/SOLR-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12622705#action_12622705 ]
Mark Miller commented on SOLR-683: ---------------------------------- >> When jetty runs out of handler threads, does it not accept new connections, >> or does it accept the connection and wait for a thread to become free to >> handle it? Not sure if this is still the case, but I believe Jetty did just use the standard socket backlog queue and set it by default to the number of service threads - so you can have that many threadless requests queued up. Dunno if they changed that recently or not. - Mark > 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.