[
https://issues.apache.org/jira/browse/GEODE-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-2125:
-----------------------------
Description:
If the Locator is started from GFSH and the cluster has one server which is
killed, network partition detection will initiate forceDisconnect which puts
the Locator in reconnect mode. To the User it will appear that the Locator
crashed for unexplained reason.
If a Locator has GFSH connected then it should notify GFSH that it is going to
forceDisconnect and go into reconnect mode. Then GFSH can notify the User so
the User is not suprised.
Attachments:
* 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
was:
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
> 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
> Affects Versions: 1.0.0-incubating
> Reporter: Kirk Lund
> Assignee: 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 puts
> the Locator in reconnect mode. To the User it will appear that the Locator
> crashed for unexplained reason.
> If a Locator has GFSH connected then it should notify GFSH that it is going
> to forceDisconnect and go into reconnect mode. Then GFSH can notify the User
> so the User is not suprised.
> Attachments:
> * 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)
