[
https://issues.apache.org/jira/browse/SOLR-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-5232:
------------------------------
Attachment: SOLR-5232.patch
This patch address a performance issue when you were sending few docs per
request to replicas (1 replica per request was really bad).
This was because each request runner would wait 250ms when the queue was empty
just in case something came along. That was huge.
This patch waits for 0ms, which removes the issue for the few updates per
request case and should not hurt the bulk docs per request case noticeably
because we are using a queue of 100 anyway.
> 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
> 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: [email protected]
For additional commands, e-mail: [email protected]
