[
https://issues.apache.org/jira/browse/SOLR-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13800043#comment-13800043
]
Mark Miller commented on SOLR-5232:
-----------------------------------
That means you were not liking seeing the same semaphore distrib lock that
SOLR-5216 is about (that semaphore no longer exists) and there is something
else going on with your setup.
> SolrCloud should distribute updates via streaming rather than buffering.
> ------------------------------------------------------------------------
>
> Key: SOLR-5232
> URL: https://issues.apache.org/jira/browse/SOLR-5232
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Reporter: Mark Miller
> Assignee: Mark Miller
> Priority: Critical
> Fix For: 4.6, 5.0
>
> Attachments: SOLR-5232.patch, SOLR-5232.patch, SOLR-5232.patch,
> SOLR-5232.patch, SOLR-5232.patch, SOLR-5232.patch
>
>
> The current approach was never the best for SolrCloud - it was designed for a
> pre SolrCloud Solr - it also uses too many connections and threads - nailing
> that down is likely wasted effort when we should really move away from
> explicitly buffering docs and sending small batches per thread as we have
> been doing.
--
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
