You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Jens Deppe (JIRA)" <ji...@apache.org> on 2017/11/14 14:50:01 UTC

[jira] [Created] (GEODE-3975) Scary message when shutting down entire cluster

Jens Deppe created GEODE-3975:
---------------------------------

             Summary: Scary message when shutting down entire cluster
                 Key: GEODE-3975
                 URL: https://issues.apache.org/jira/browse/GEODE-3975
             Project: Geode
          Issue Type: Bug
          Components: gfsh
            Reporter: Jens Deppe


With one locator and one server started, if I shutdown the entire cluster I see the following:
{noformat}
gfsh>start locator --name=locator1
Starting a Geode Locator in /Users/jdeppe/git/gemfire-develop/open/locator1...
....

gfsh>start server --name=server1 --locators=localhost[10334] --server-port=0
Starting a Geode Server in /Users/jdeppe/git/gemfire-develop/open/server1...
....

gfsh>shutdown --include-locators=true
As a lot of data in memory will be lost, including possibly events in queues, do you really want to shutdown the entire distributed system? (Y/n): y
Shutdown is triggered

Failed to restart: java.io.IOException: Failed to get a RMI stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: 10.118.33.247; nested exception is:
    java.net.ConnectException: Connection refused (Connection refused)]
gfsh>
No longer connected to 10.118.33.247[1099].
Failed to call the method close():java.rmi.ConnectException: Connection refused to host: 10.118.33.247; nested exception is:
    java.net.ConnectException: Connection refused (Connection refused)
Failed to check connection: java.rmi.NoSuchObjectException: no such object in table
stopping
gfsh>
{noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)