Archives of Support Questions (Read Only)

This is an archived board for historical reference. Information and links may no longer be available or relevant
Announcements
This board is archived and read-only for historical reference. To ask a new question, please post a new topic on the appropriate active board.

bin/solr status throwing an error "clusterstatus the collection time out:180s"

avatar
Guru

I have setup my cluster in cloud mode with 3 nodes and it was running fine. I have created two collections as well. But when I was enabling ranger plugin then I had to restart all the nodes. I stopped all the solr instance and started once again then following error occurred. I can see solr UI and my collection but I can't see cluster status in command line as getting below error.

solr@m1 solr]$ bin/solr stop -all

Sending stop command to Solr running on port 8983 ... waiting 5 seconds to allow Jetty process 15060 to stop gracefully.

[solr@m1 solr]$ bin/solr start -c -z m1.hdp22:2181,m2.hdp22:2181,w1.hdp22:2181 -Dsolr.directoryFactory=HdfsDirectoryFactory -Dsolr.lock.type=hdfs

Started Solr server on port 8983 (pid=24214). Happy searching!

[solr@m1 solr]$ bin/solr status

Found 1 Solr nodes:

Solr process 24214 running on port 8983

Failed to get system information from http://localhost:8983/solr/ due to: org.apache.solr.client.solrj.SolrServerException: clusterstatus the collection time out:180s

at org.apache.solr.util.SolrCLI.getJson(SolrCLI.java:537)

at org.apache.solr.util.SolrCLI.getJson(SolrCLI.java:471)

at org.apache.solr.util.SolrCLI$StatusTool.getCloudStatus(SolrCLI.java:721)

at org.apache.solr.util.SolrCLI$StatusTool.reportStatus(SolrCLI.java:704)

at org.apache.solr.util.SolrCLI$StatusTool.runTool(SolrCLI.java:662)

at org.apache.solr.util.SolrCLI.main(SolrCLI.java:215)

I went through following jira which tell it is bug but I am not sure how to solve this issue,so can someone please help me to get it resolved.

https://issues.apache.org/jira/browse/SOLR-7018

Note : I am using solr-spec-version":"5.2.1 version.

1 ACCEPTED SOLUTION

avatar
Guru

I have solved it by applying following steps.

- Stop all Solr instances - Stop all Zookeeper instances - Start all Zookeeper instances - Start Solr instances one at a time.

View solution in original post

1 REPLY 1

avatar
Guru

I have solved it by applying following steps.

- Stop all Solr instances - Stop all Zookeeper instances - Start all Zookeeper instances - Start Solr instances one at a time.