Let me propose a slightly different approach ;-) Since you don’t need Solrcloud to support scaling needs, but instead for redundancy, then I like to set things up where my indexer just sends the updates to TWO SEPARATE single server Solr nodes. This is great for a number of reasons:
1) Green/Blue deployments. I can upgrade one Solr and leave the other alone. 2) I can A/B test by deploying new relevance configs to one Solr and then compare results to the other. 3) If I am in the cloud, well I can drop one Solr on AWS and the other on GCP or another cloud provider. Eric > On Mar 14, 2022, at 1:28 AM, Sam Lee <samlee...@yahoo.com.INVALID> wrote: > > On 2022/03/13 22:22:48 Shawn Heisey wrote: >> Zookeeper has fairly low system requirements compared to Solr, so using >> a third machine with lower specs to just run the tie-breaker ZK is a >> good way to go. >> >> Note that you'll only have full redundancy at the client level with that >> setup if your client is ZK-aware. The only Solr client I know about >> that's ZK aware is the Java client, which is part of Solr itself as well >> as being a standalone client. > > Thank you for bringing this potential issue to my attention. > > By "standalone client", do you mean that I could use SolrJ on a separate > server where no Solr instance is running? i.e. use the client to > remotely connect to SolrCloud. > > By the way, the most popular Python client, pysolr, seems to support > SolrCloud mode. [1] > >> For full redundancy with HTTP-only clients you'll need a virtual IP >> address that can be shared among the servers, and have a load balancer >> listening on the virtual IP. Setting that up is done with software >> other than Solr and ZK, so it's not on-topic for this mailing list. >> Depending on the capabilities of the third server, it could be the >> primary for load-balancing as well as the third machine for ZK. >> That's what I would do with limited resources. > > I think I will stick to ZooKeeper-aware clients if I choose to go the > SolrCloud route. Using the SolrJ "CloudSolrClient" looks like a much > simpler solution than setting up all the infrastructure required for > achieving high availability with HTTP-only clients. > > > [1]: https://github.com/django-haystack/pysolr _______________________ Eric Pugh | Founder & CEO | OpenSource Connections, LLC | 434.466.1467 | http://www.opensourceconnections.com <http://www.opensourceconnections.com/> | My Free/Busy <http://tinyurl.com/eric-cal> Co-Author: Apache Solr Enterprise Search Server, 3rd Ed <https://www.packtpub.com/big-data-and-business-intelligence/apache-solr-enterprise-search-server-third-edition-raw> This e-mail and all contents, including attachments, is considered to be Company Confidential unless explicitly stated otherwise, regardless of whether attachments are marked as such.
