Thanks Erick, that's extremely insightful. I'm not using batching and that's the reason I was exploring ConcurrentUpdateSolrClient. Currently, N threads are reusing the same CloudSolrClient to send data to Solr. Ofcourse, the single point of failure was my biggest concern with ConcurrentUpdateSolrClient, thanks for clarifying my doubt.
"You also want to be a little careful how hard you drive Solr if you're also serving queries at the same time, the more cycles you use for indexing the fewer are available to serve queries." Our solr servers are also used to serve queries (50-100/minute). Our hard commit set at 10 minutes while soft commit is disabled. Are there any best practices (I know it's too generic, but specifically around indexing) that I should follow? -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
