I would actually like to write a load balancer itself, but I want it to be able to send the data as efficiently as possible. I know how to read ZK data, but I don’t know how can I figure out which shard is responsible upon data that I have in a document that I want to index.
> On 11. Feb 2019, at 17:23, Walter Underwood <wun...@wunderwood.org> wrote: > > We send all updates to the load balancer, so they’ll end up on the wrong > shard, not on the leader, etc. Indexing speed is still limited by the CPU > available on each leader. I don’t think that sending the update to the right > leader makes any improvement in throughput. > > On the other hand, the CloudSolrClient ignores errors from Solr, which makes > it unacceptable for production use. > > I would stay with your current indexing client and worry about something else. > > wunder > Walter Underwood > wun...@wunderwood.org > http://observer.wunderwood.org/ (my blog)
