[
https://issues.apache.org/jira/browse/SOLR-5216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13764057#comment-13764057
]
Mark Miller commented on SOLR-5216:
-----------------------------------
I think the only thing that this patch could possibly do is eliminate the
deadlock, but allow for more threads. I only expect up to a 2x max use in
threads, but it could be off and allow for more than that if there is some
small bug I'm missing. In any case, I'm sure the idea is the right one for the
deadlock. I worry the problems you get after many hours might be due to the
sheer number of threads and requests. I worry about spending too much time
trying to get this solution working though - it might be energy better spent
changing things towards a better direction - SOLR-5232: SolrCloud should
distribute updates via streaming rather than buffering.
> 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.5, 5.0
>
> Attachments: SOLR-5216.patch
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
