Using ZooKeeper to Manage Configuration Files

When you try SolrCloud for the first time using the bin/solr -e cloud, the related configset gets uploaded to ZooKeeper automatically and is linked with the newly created collection.

The below command would start SolrCloud with the default collection name (gettingstarted) and default configset (_default) uploaded and linked to it.

You can also explicitly upload a configuration directory when creating a collection using the bin/solr script with the -d option, such as:

The create command will upload a copy of the _default configuration directory to ZooKeeper under /configs/mycollection. Refer to the Solr Control Script Reference page for more details about the create command for creating collections.

Once a configuration directory has been uploaded to ZooKeeper, you can update them using the Solr Control Script

In production situations, Config Sets can also be uploaded to ZooKeeper independent of collection creation using either Solr’s Solr Control Script or the CloudSolrClient.uploadConfig java method.

The below command can be used to upload a new configset using the bin/solr script.

It is strongly recommended that the configurations be kept in a version control system, Git, SVN or similar.

To update or change your SolrCloud configuration files:

If you will share the same ZooKeeper instance with other applications you should use a chroot in ZooKeeper. Please see ZooKeeper chroot for instructions.

There are certain configuration files containing cluster wide configuration. Since some of these are crucial for the cluster to function properly, you may need to upload such files to ZooKeeper before starting your Solr cluster for the first time. Examples of such configuration files (not exhaustive) are solr.xml, security.json and clusterprops.json.

If you for example would like to keep your solr.xml in ZooKeeper to avoid having to copy it to every node’s solr_home directory, you can push it to ZooKeeper with the bin/solr utility (Unix example):