You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Steve Rowe (JIRA)" <ji...@apache.org> on 2015/01/22 18:34:35 UTC

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

Steve Rowe created SOLR-7018:
--------------------------------

             Summary: "bin/solr status" error after calling "bin/solr stop" against a cluster started using "bin/solr -e cloud"
                 Key: SOLR-7018
                 URL: https://issues.apache.org/jira/browse/SOLR-7018
             Project: Solr
          Issue Type: Bug
            Reporter: Steve Rowe
            Priority: Minor


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:

{noformat}
$ 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)
{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org