A ZooKeeper Command Line Interface (CLI) script is available to allow you to interact directly with Solr configuration files stored in ZooKeeper.
While Solr’s Administration UI includes pages dedicated to the state of your SolrCloud cluster, it does not allow you to download or modify related configuration files.
| See the section Cloud Screens for more information about using the Admin UI screens. |
The ZooKeeper CLI scripts found in server/scripts/cloud-scripts let you upload configuration information to ZooKeeper, in the same ways shown in the examples in Parameter Reference. It also provides a few other commands that let you link collection sets to collections, make ZooKeeper paths or clear them, and download configurations from ZooKeeper to the local filesystem.
Many of the functions provided by the zkCli.sh script are also provided by the Solr Control Script, which may be more familiar as the start script ZooKeeper maintenance commands are very similar to Unix commands.
|
Solr’s zkcli.sh vs ZooKeeper’s zkCli.sh
The ZooKeeper’s |
Using Solr’s ZooKeeper CLI
Use the help option to get a list of available commands from the script itself, as in ./server/scripts/cloud-scrips/zkcli.sh help.
Both zkcli.sh (for Unix environments) and zkcli.bat (for Windows environments) support the following command line options:
-cmd <arg>-
The CLI Command to be executed. This parameter is mandatory. The following commands are supported:
-
bootstrap -
upconfig -
downconfig -
linkconfig -
makepath -
getandgetfile -
putandputfile -
clear -
list -
ls -
clusterprop
-
-zor-zkhost <locations>-
ZooKeeper host address. This parameter is mandatory for all CLI commands.
-cor-collection <name>-
For
linkconfig: name of the collection. -dor-confdir <path>-
For
upconfig: a directory of configuration files. For downconfig: the destination of files pulled from ZooKeeper -hor-help-
Display help text.
-nor-confname <arg>-
For
upconfig,linkconfig,downconfig: name of the configuration set. -ror-runzk <port>-
Run ZooKeeper internally by passing the Solr run port; only for clusters on one machine.
-sor-solrhome <path>-
For
bootstrapor when using-runzk: the mandatory solrhome location. -name <name>-
For
clusterprop: the mandatory cluster property name. -val <value>-
For
clusterprop: the cluster property value. If not specified, null will be used as value.
|
The short form parameter options may be specified with a single dash (eg: The long form parameter options may be specified using either a single dash (eg: |
ZooKeeper CLI Examples
Below are some examples of using the zkcli.sh CLI which assume you have already started the SolrCloud example (bin/solr -e cloud -noprompt)
If you are on Windows machine, simply replace zkcli.sh with zkcli.bat in these examples.
Upload a configuration directory
./server/scripts/cloud-scripts/zkcli.sh -zkhost 127.0.0.1:9983 -cmd upconfig -confname my_new_config -confdir server/solr/configsets/basic_configs/confBootstrap ZooKeeper from existing SOLR_HOME
./server/scripts/cloud-scripts/zkcli.sh -zkhost 127.0.0.1:2181 -cmd bootstrap -solrhome /var/solr/data|
Bootstrap with chroot
Using the boostrap command with a zookeeper chroot in the |
Put arbitrary data into a new ZooKeeper file
./server/scripts/cloud-scripts/zkcli.sh -zkhost 127.0.0.1:9983 -cmd put /my_zk_file.txt 'some data'Put a local file into a new ZooKeeper file
./server/scripts/cloud-scripts/zkcli.sh -zkhost 127.0.0.1:9983 -cmd putfile /my_zk_file.txt /tmp/my_local_file.txtLink a collection to a configuration set
./server/scripts/cloud-scripts/zkcli.sh -zkhost 127.0.0.1:9983 -cmd linkconfig -collection gettingstarted -confname my_new_configCreate a new ZooKeeper path
This can be useful to create a chroot path in ZooKeeper before first cluster start.
./server/scripts/cloud-scripts/zkcli.sh -zkhost 127.0.0.1:2181 -cmd makepath /solrSet a cluster property
This command will add or modify a single cluster property in clusterprops.json. Use this command instead of the usual getfile → edit → putfile cycle.
Unlike the CLUSTERPROP command on the Collections API, this command does not require a running Solr cluster.
./server/scripts/cloud-scripts/zkcli.sh -zkhost 127.0.0.1:2181 -cmd clusterprop -name urlScheme -val https