On 7/22/2016 1:22 AM, Aristedes Maniatis wrote: > I'm not new to Solr, but I'm upgrading from Solr 4 to 5 and needing to > use the new Zookeeper configuration requirement. It is adding a lot of > extra complexity to our deployment and I want to check that we are > doing it right.
Zookeeper is not required for Solr 5, or even for Solr 6. It's only required for SolrCloud. SolrCloud is an operating mode that is not mandatory. SolrCloud has been around since Solr 4.0.0. > The problem we want to escape is that this configuration causes > outages and other random issues each time the Solr master does a full > reload. It shouldn't, but it does and hopefully the new SolrCluster > will be better. The fact that Solr does a full replication when the master is restarted/reloaded is a bug. This bug is fixed in 5.5.2 and 6.1.0. https://issues.apache.org/jira/browse/SOLR-9036 If you *do* want to run in cloud mode, then you will need to use zkcli to upload config changes to zookeeper and then issue a collection reload with the Collections API. This will find and reload all the cores related to that collection, across the entire cloud. You have the option of using the ZkCLI java class, or the zkcli.sh script that can be found in all 5.x and 6.x installs at server/scripts/cloud-scripts. As of version 5.3, the jars required for zkcli are already unpacked before Solr is started. Thanks, Shawn
