You may not need to deal with any of this. The default CloudSolrClient call creates a new LBHttpSolrClient for you. So unless you're doing something custom with any LBHttpSolrClient you create, you don't need to create one yourself.
Second, the default for CloudSolrClient.add() is to take the list of documents you provide into sub-lists that consist of the docs destined for a particular shard and sends those to the leader. Do the default not work for you? Best, Erick On Wed, May 9, 2018 at 2:54 AM, Bernd Fehling <bernd.fehl...@uni-bielefeld.de> wrote: > Hi list, > > while going from single core master/slave to cloud multi core/node > with leader/replica I want to change my SolrJ loading, because > ConcurrentUpdateSolrClient isn't cloud aware and has performance > impacts. > I want to use CloudSolrClient with LBHttpSolrClient and updates > should only go to shard leaders. > > Question, what is the difference between sendUpdatesOnlyToShardLeaders > and sendDirectUpdatesToShardLeadersOnly? > > Regards, > Bernd
