SOLR-4816 won't address this - it will just speed up *different* parts. There
are other things that will need to be done to speed up that part.
- Mark
On Jul 26, 2013, at 3:53 PM, Erick Erickson erickerick...@gmail.com wrote:
This is current a hard-coded limit from what I've understood. From
Why wouldn't it? Or are you saying that the routing to replicas
from the leader also 10/packet? Hmmm, hadn't thought of that...
On Mon, Jul 29, 2013 at 7:58 AM, Mark Miller markrmil...@gmail.com wrote:
SOLR-4816 won't address this - it will just speed up *different* parts. There
are other
Yes, the internal document forwarding path is different and does not use the
CloudSolrServer. It currently works with a buffer of 10.
- Mark
On Jul 29, 2013, at 3:10 PM, Erick Erickson erickerick...@gmail.com wrote:
Why wouldn't it? Or are you saying that the routing to replicas
from the
This is current a hard-coded limit from what I've understood. From what
I remember, Mark said Yonik said that there are reasons to make the
packets that size. But whether this is empirically a Good Thing I don't know.
SOLR-4816 will address this a different way by making SolrJ batch up
the docs
Hi,
Context:
* https://issues.apache.org/jira/browse/SOLR-4956
*
http://search-lucene.com/c/Solr:/core/src/java/org/apache/solr/update/SolrCmdDistributor.java%7C%7CmaxBufferedAddsPerServer
As you can see, maxBufferedAddsPerServer = 10.
We have an app that sends 20K docs to SolrCloud using
