Hi Umberto, you can take inspiration from the org.apache.solr.client.solrj.impl.CloudSolrClient (if you are familiar with Java code).
Rather than round robin, you can leverage Zookeeper to know who's alive at the moment (check the CloudSolrClient builder that takes Zookeeper nodes URLs as input). In that SolrJ class you see both indexing/querying approaches. Hope this helps, Cheers -------------------------- *Alessandro Benedetti* Director @ Sease Ltd. *Apache Lucene/Solr Committer* *Apache Solr PMC Member* e-mail: a.benede...@sease.io *Sease* - Information Retrieval Applied Consulting | Training | Open Source Website: Sease.io <http://sease.io/> LinkedIn <https://linkedin.com/company/sease-ltd> | Twitter <https://twitter.com/seaseltd> | Youtube <https://www.youtube.com/channel/UCDx86ZKLYNpI3gzMercM7BQ> | Github <https://github.com/seaseltd> On Tue, 9 Jan 2024 at 15:20, Shawn Heisey <elyog...@elyograg.org.invalid> wrote: > On 1/8/24 10:32, Facchin Umberto wrote: > > If server2 or server3 are down everything continues to work (even the > updates), but if server1 is down then everything stops, obviously. > > Solr has no features to get around this. > > What you need is something that manages a virtual IP address among > multiple servers. Optionally you could have that virtual IP address > live on a set of machines that operate a load balancer sitting in front > of your SolrCloud cluster. > > Things I have seen that can do this include: > > pacemaker > keepalived > ucarp > > Thanks, > Shawn >
