[
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 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
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.
> Network partition forceDisconnect leave Locator process running
> ---------------------------------------------------------------
>
> Key: GEODE-2125
> URL: https://issues.apache.org/jira/browse/GEODE-2125
> Project: Geode
> Issue Type: Bug
> Components: management, membership
> 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)
