lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SOLR-683) Distributed Search / Shards Deadlock
Date Thu, 14 Aug 2008 21:07:44 GMT

    [ https://issues.apache.org/jira/browse/SOLR-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12622700#action_12622700
] 

Yonik Seeley commented on SOLR-683:
-----------------------------------

Hmmm I see this was just committed, but are we sure it works?
Isn't acceptQueueSize just the network level connection queue size for the socket (as normally
set by the listen sys call)?
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?
If the former, then this patch should work.  If the latter, it won't.

> 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.


Mime
View raw message