One comment to complicate Erick's already-good advice. > If a doc that needs to go to shard2 is received by a replica on shard1, it > must be forwarded to the leader of shard1, introducing an extra hop.
Definitely true, but I don't think that's the only factor in the relative performance of CUSC vs CSC. CUSC responds asynchronously when you're using it for updates, which lets users continue on to prepare the next set of docs while a CloudSolrClient might still be waiting to hear back from Solr. I benchmarked this recently and was surprised to see that ConcurrentUpdateSolrClient actually came out ahead in some setups. Now I'm not trying to say that CUSC performs better than CSC, just that "It Depends" (Erick's TM) on the rest of your ETL code, on the topology of your SolrCloud cluster, etc. Good luck! Jason On Wed, Oct 24, 2018 at 6:49 PM shamik <sham...@gmail.com> wrote: > > Thanks Erick, appreciate your help > > > > -- > Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
