There are all sorts of problems with the primary/secondary approach. How do you know the secondary is working? How do you deal with cold caches on the secondary when it suddenly gets lots of load?
Instead, size the cluster with the number of hosts you need, then add one. Send traffic to all of them. If any of them goes down, you have the capacity to handle the traffic. This is called “N+1 provisioning”. This was our rule at Netflix a dozen years ago, running Solr 1.3. I do it the same way today with large sharded clusters, one extra per shard. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) > On Jan 11, 2021, at 2:41 AM, DAVID MARTIN NIETO <dmart...@viewnext.com> wrote: > > I believe Solr dont have this configuration, you need a load balancer with > that configuration mode for that. > > Kind regards. > > > ________________________________ > De: Kaushal Shriyan <kaushalshri...@gmail.com> > Enviado: lunes, 11 de enero de 2021 11:32 > Para: solr-user@lucene.apache.org <solr-user@lucene.apache.org> > Asunto: Apache Solr in High Availability Primary and Secondary node. > > Hi, > > We are running Apache Solr 8.7.0 search service on CentOS Linux release > 7.9.2009 (Core). > > Is there a way to set up the Solr search service in High Availability Mode > in the Primary and Secondary node? For example, if the primary node is down > secondary node will take care of the service. > > Best Regards, > > Kaushal
