[
https://issues.apache.org/jira/browse/SOLR-5216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13834886#comment-13834886
]
Erick Erickson commented on SOLR-5216:
--------------------------------------
This shouldn't affect single-shard setups. The deadlock,
as I remember, showed up when lots of nodes split up
incoming batches of documents to forward to lots of
leaders. Since a single shard won't split up the documents,
I doubt this is the root of what you're seeing.
But yeah, a stack trace would tell us for certain.
And Mark committed SOLR-5232 which uses a different
mechanism anyway.
To recap: I doubt this issue is a problem in single-shard
setups.
> Document updates to SolrCloud can cause a distributed deadlock.
> ---------------------------------------------------------------
>
> Key: SOLR-5216
> URL: https://issues.apache.org/jira/browse/SOLR-5216
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Reporter: Mark Miller
> Assignee: Mark Miller
> Priority: Critical
> Fix For: 4.6, 5.0
>
> Attachments: SOLR-5216.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
