[SOLR-7018] "bin/solr status" error after calling "bin/solr stop" against a cluster started using "bin/solr -e cloud"

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 5.0, 6.0
• Assignee: Timothy Potter
• Reporter: Steven Rowe
• Created: 22/Jan/15 17:34
• Updated: 09/May/16 18:52
• Resolved: 22/Jan/15 19:19

Description

Start a cluster using bin/solr -e cloud -noprompt.

Run bin/solr stop. This will only stop one of the two nodes, using the default port 8983. (This in itself is a problem.)

Run bin/solr status. Previously I thought that this process hung because it took a while to return, but just now I tried it again and got this:

$ bin/solr status

Found 1 Solr nodes: 

Solr process 88680 running on port 7574
Failed to get system information from http://localhost:7574/solr/ due to: org.apache.solr.client.solrj.SolrServerException: KeeperErrorCode = ConnectionLoss for /overseer/collection-queue-work/qn-
	at org.apache.solr.util.SolrCLI.getJson(SolrCLI.java:513)
	at org.apache.solr.util.SolrCLI.getJson(SolrCLI.java:456)
	at org.apache.solr.util.SolrCLI$StatusTool.getCloudStatus(SolrCLI.java:697)
	at org.apache.solr.util.SolrCLI$StatusTool.reportStatus(SolrCLI.java:680)
	at org.apache.solr.util.SolrCLI$StatusTool.runTool(SolrCLI.java:638)
	at org.apache.solr.util.SolrCLI.main(SolrCLI.java:203)