We have integrated Solr 5.3.1 into our product. During installation customers have the option of setting up a single Solr instance, or for high availability deployments, multiple Solr instances in a master/slave configuration.
We are looking at migrating to SolrCloud for HA deployments, but are wondering if it makes sense to also use SolrCloud in non-HA deployments? Our thought is that this would simplify things. We could use the same approach for deploying our schema.xml and other configuration files on all systems, we could always use the SolrJ CloudSolrClient class to communicate with Solr, etc. Would it make sense to use the embedded Zookeeper instance in this situation? I have seen warning that the embedded Zookeeper should not be used in production deployments, but the reason generally given is that if Solr goes down Zookeeper will also go down, which doesn't seem relevant here. Are there other reasons not to use the embedded Zookeeper? More generally, are there downsides to using SolrCloud with a single Zookeeper node and single Solr node? Would appreciate any feedback. Thanks, Andy
