Also, since CloudSolrClient is ZK aware it is notified when any Solr instances go up and down so it will take the appropriate action. Also, when indexing CloudSolrClient will send updates to the correct leader, reducing the hops for indexing documents.
Short form: CloudSolrClient is preferred over LBHttpSolrClient. Best, Erick On Mon, Jul 17, 2017 at 12:15 PM, Amrit Sarkar <sarkaramr...@gmail.com> wrote: > S G, > > Not sure about the documentation but: > > The CloudSolrClient uses a connection to zookeeper to extract cluster > information like who is a the leader for a shard in a solr collection. To > create a CloudSolrClient all you specify is the zookeepers and which > collection you want to work with. Behind the scenes solrj will load balance > and send the request to the right "shard" in the cluster. The > CloudSolrClient is better if you have a cluster of multiple solr nodes > across multiple machines. > > While in LBHttpSolrClient, load balancing is done using a simple > round-robin on the list of servers. > > Hope this helps. > > Amrit Sarkar > Search Engineer > Lucidworks, Inc. > 415-589-9269 > www.lucidworks.com > Twitter http://twitter.com/lucidworks > LinkedIn: https://www.linkedin.com/in/sarkaramrit2 > > On Mon, Jul 17, 2017 at 11:38 PM, S G <sg.online.em...@gmail.com> wrote: > >> Hi, >> >> Does anyone know if CloudSolrClient is preferred over LBHttpSolrClient ? >> If yes, why so and has there been any good performance benefits documented >> anywhere? >> >> Thanks >> SG >>
