You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Kirk Lund (JIRA)" <ji...@apache.org> on 2016/11/17 22:53:58 UTC

[jira] [Updated] (GEODE-2125) GFSH should tell user that Locator it's connected to has gone into reconnect

     [ https://issues.apache.org/jira/browse/GEODE-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kirk Lund updated GEODE-2125:
-----------------------------
    Summary: GFSH should tell user that Locator it's connected to has gone into reconnect  (was: Network partition forceDisconnect leaves crippled Locator process running)

> GFSH should tell user that Locator it's connected to has gone into reconnect
> ----------------------------------------------------------------------------
>
>                 Key: GEODE-2125
>                 URL: https://issues.apache.org/jira/browse/GEODE-2125
>             Project: Geode
>          Issue Type: Bug
>          Components: management, membership
>    Affects Versions: 1.0.0-incubating
>            Reporter: Kirk Lund
>         Attachments: locator_failure-logs.txt, thread_dump.txt
>
>
> If the Locator is started from GFSH and the cluster has one server which is killed, network partition detection will initiate forceDisconnect which shuts down the Locator. The Locator process, however, continues to run and any attempts to use stop locator or status locator will fail.
> The Locator log file is attached as locator_failure-logs.txt
> The Locator thread dump (via jstack) AFTER it has shut down due to forceDisconnect is attached as thread_dump.txt



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