Apache Solr Reference Guide Covering Apache Solr 6.0

Found 2 Solr nodes:
Solr process 39920 running on port 7574
{
"solr_home":"/Applications/Solr/example/cloud/node2/solr/",
"version":"X.Y.0",
"startTime":"2015-02-10T17:19:54.739Z",
"uptime":"1 days, 23 hours, 55 minutes, 48 seconds",
"memory":"77.2 MB (%15.7) of 490.7 MB",
"cloud":{
"ZooKeeper":"localhost:9865",
"liveNodes":"2",
"collections":"2"}}
Solr process 39827 running on port 8865
{
"solr_home":"/Applications/Solr/example/cloud/node1/solr/",
"version":"X.Y.0",
"startTime":"2015-02-10T17:19:49.057Z",
"uptime":"1 days, 23 hours, 55 minutes, 54 seconds",
"memory":"94.2 MB (%19.2) of 490.7 MB",
"cloud":{
"ZooKeeper":"localhost:9865",
"liveNodes":"2",
"collections":"2"}}
Healthcheck
The healthcheck command generates a JSON-formatted health report for a collection when running in SolrCloud
mode. The health report provides information about the state of every replica for all shards in a collection,
including the number of committed documents and its current state.
bin/solr healthcheck [options]
bin/solr healthcheck -help
Available Parameters
Parameter Description Example
-c
Name of the collection to run a healthcheck against (required).
bin/solr
healthcheck
-c
gettingstarted
-z ZooKeeper connection string, defaults to localhost:9983. If you are running
Solr on a port other than 8983, you will have to specify the ZooKeeper
connection string. By default, this will be the Solr port + 1000.
bin/solr
healthcheck
-z
localhost:2181
Below is an example healthcheck request and response using a non-standard ZooKeeper connect string, with 2
nodes running:
Apache Solr Reference Guide 6.0
20