[ https://issues.apache.org/jira/browse/SOLR-7018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Potter resolved SOLR-7018.
----------------------------------
Resolution: Fixed
Fix Version/s: Trunk
5.0
> "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
> Assignee: Timothy Potter
> Priority: Blocker
> Fix For: 5.0, Trunk
>
> Attachments: SOLR-7018.patch
>
>
> 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
|