You’re on the right idea, in my opinion. Three identical “slave”servers with one “master” with an nginx server on each one “slave” witth the servers augmented. N1 has a 2—>s3 n2 has n3->s2 n3 has s3->s1 and all three finally fall to master. You can get 5 9’s like this.
Pro tip keep all action on one until it falls, and never use over 31 fb heap size Just is just a trial and error and complete success option snd no need of complications with zk -Dave > On Mar 13, 2022, at 3:48 PM, Sam Lee <samlee...@yahoo.com.invalid> wrote: > > How do I run Apache Solr on two servers such that I will still be able > to index and query even if one of the servers is taken offline? In other > words, I am looking for high availability with automatic failover. > > I have looked at SolrCloud. However, it uses Apache ZooKeeper which > requires at least 3 servers to be able to tolerate the failure of 1 > server. Are there alternative methods? > > I only have two servers that are able to run Solr. Supposing I have a > third low-spec server, is it a good idea to run Solr (SolrCloud) on only > two of the three servers, while running ZooKeeper on all three servers? > However, this looks like a waste because the third server would > essentially be doing nothing. Is there a better method with standalone > Solr?
