Uploaded image for project: 'Solr'
  1. Solr
  2. SOLR-7018

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

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.0, 6.0
    • Component/s: None
    • Labels:
      None

      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)
      

        Attachments

        1. SOLR-7018.patch
          2 kB
          Timothy Potter

          Activity

            People

            • Assignee:
              thelabdude Timothy Potter
              Reporter:
              steve_rowe Steve Rowe
            • Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: