[
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 in the
Locator and leave it in reconnect mode. To the User it will appear that the
Locator crashed and GFSH lost connection:
```
gfsh>
No longer connected to 192.168.1.72[1099].
```
During the time in which the Locator is in reconnect mode, the User cannot
connect via GFSH, nor can they issue status or stop commands on it.
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.
In addition, GFSH status and stop commands should be modified to be able to
talk to a Locator in reconnect mode. GFSH start could also be modified to
report that the Locator is running in reconnect mode instead of reporting a
hung process in the Locator's directory.
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 in the
Locator and leave it in reconnect mode. To the User it will appear that the
Locator crashed for unexplained reason. During the time in which the Locator is
in reconnect mode, the User cannot connect via GFSH, nor can they issue status
or stop commands on it.
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.
In addition, GFSH status and stop commands should be modified to be able to
talk to a Locator in reconnect mode. GFSH start could also be modified to
report that the Locator is running in reconnect mode instead of reporting a
hung process in the Locator's directory.
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
> GFSH should provide information about Locators that go into reconnect mode
> --------------------------------------------------------------------------
>
> 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 in the
> Locator and leave it in reconnect mode. To the User it will appear that the
> Locator crashed and GFSH lost connection:
> ```
> gfsh>
> No longer connected to 192.168.1.72[1099].
> ```
> During the time in which the Locator is in reconnect mode, the User cannot
> connect via GFSH, nor can they issue status or stop commands on it.
> 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.
> In addition, GFSH status and stop commands should be modified to be able to
> talk to a Locator in reconnect mode. GFSH start could also be modified to
> report that the Locator is running in reconnect mode instead of reporting a
> hung process in the Locator's directory.
> 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)
