It's been a while since I've been in this deeply, but it should be something like:
sendUpdateOnlyToShardLeaders will select the leaders for each shard as the load balanced targets for update. The updates may not go to the *right* leader, but only the leaders will be chosen, followers (non leader replicas) will not be part of the load balanced server list. sendDirectUpdatesToShardLeadersOnly is the same, followers are not part of the mix, but also, updates are sent directly to the right leader as long as the right hashing field is specified (id by default). We hash the id client side and know where it should end up. Optimally, you want sendDirectUpdatesToShardLeadersOnly to be true configured with the correct id field. - Mark On Wed, May 9, 2018 at 4: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 > -- - Mark about.me/markrmiller
