Start Solr in SolrCloud mode, which will also launch the embedded ZooKeeper instance included with Solr.
This option can be shortened to simply
If you are already running a ZooKeeper ensemble that you want to use instead of the embedded (single-node) ZooKeeper, you should also either specify
solr.in.cmd (see instructions) or pass the -z parameter.
For more details, see the section SolrCloud Mode below.
bin/solr start -c
Define a server directory, defaults to
server (as in,
$SOLR_HOME/server). It is uncommon to override this option. When running multiple instances of Solr on the same host, it is more common to use the same server directory for each instance and use a unique Solr home directory using the -s option.
bin/solr start -d newServerDir
Start Solr with an example configuration. These examples are provided to help you get started faster with Solr generally, or just try a specific feature.
The available options are:
Start Solr in the foreground; you cannot use this option when running examples with the -e option.
bin/solr start -f
Start Solr with the defined hostname. If this is not specified, 'localhost' will be assumed.
bin/solr start -h search.mysolr.com
Start Solr with the defined value as the min (-Xms) and max (-Xmx) heap size for the JVM.
bin/solr start -m 1g
Start Solr and suppress any prompts that may be seen with another option. This would have the side effect of accepting all defaults implicitly.
For example, when using the "cloud" example, an interactive session guides you through several options for your SolrCloud cluster. If you want to accept all of the defaults, you can simply add the -noprompt option to your request.
bin/solr start -e cloud -noprompt
Start Solr on the defined port. If this is not specified, '8983' will be used.
bin/solr start -p 8655
solr.solr.home system property; Solr will create core directories under this directory. This allows you to run multiple Solr instances on the same host while reusing the same server directory set using the
If set, the specified directory should contain a
solr.xml file, unless
solr.xml exists in ZooKeeper. The default value is
This parameter is ignored when running examples (
-e), as the
solr.solr.home depends on which example is run.
bin/solr start -s newHome
Be more verbose. This changes the logging level of log4j from
DEBUG, having the same effect as if you edited
bin/solr start -f -v
Be more quiet. This changes the logging level of log4j from
WARN, having the same effect as if you edited
log4j2.xml accordingly. This can be useful in a production setting where you want to limit logging to warnings and errors.
bin/solr start -f -q
Start Solr with verbose messages from the start script.
bin/solr start -V
Start Solr with the defined ZooKeeper connection string. This option is only used with the -c option, to start Solr in SolrCloud mode. If
ZK_HOST is not specified in
solr.in.cmd and this option is not provided, Solr will start the embedded ZooKeeper instance and use that instance for SolrCloud operations.
bin/solr start -c -z server1:2181,server2:2181
If attempting to start Solr as the root user, the script will exit with a warning that running Solr as "root" can cause problems. It is possible to override this warning with the -force parameter.
sudo bin/solr start -force