Glad you can solve it one way or the other. I do wonder, though what's really going on, the fact that your original case just hung is kind of disturbing.
50K is still a lot, and Yonik's comment is well taken. I did some benchmarking (not ConcurrentUpdateSolrServer, HttpSolrClient as I remember) and got diminishing returns pretty rapidly after the first few, see: https://lucidworks.com/blog/2015/10/05/really-batch-updates-solr-2/ There was a huge jump going from 1 to 10, a smaller (percentage wise) jump going from 10 to100 and not much to talk about between 100 and 1,000 (single threaded, YMMV of course). Best Erick On Fri, Oct 30, 2015 at 6:26 AM, Yonik Seeley <ysee...@gmail.com> wrote: > On Thu, Oct 29, 2015 at 5:28 PM, Erick Erickson <erickerick...@gmail.com> > wrote: >> Try making batches of 1,000 docs and sending them through instead. > > The other thing about ConcurrentUpdateSolrClient is that it will > create batches itself while streaming. > For example, if you call add a number of times very quickly, those > will all be put in the same update request as they are being streamed > (you get the benefits of batching without the latency it would > normally come with.) > > So I guess I'd advise to not batch yourself unless it makes more sense > for your document processing for other reasons. > > -Yonik
