Anton Mironenko created GEODE-3037:
--------------------------------------
Summary: A server process shuts down quitely when no locator is
available
Key: GEODE-3037
URL: https://issues.apache.org/jira/browse/GEODE-3037
Project: Geode
Issue Type: Bug
Components: membership
Reporter: Anton Mironenko
If I start a server, when no one locator is available, it shuts down quietly
without any message in the log. Why doesn't it wait for a locator to start? Why
no message in the log?
The expected behavior is that a cluster nodes can be started in any order,
waiting each other if needed.
Here are the steps to reproduce, please use GEODE-3003 for zip files.
Test preparation:
---------------------
Here are two attached zip files - "geode-host1.zip" and "geode-host2.zip"
1) unzip "geode-host1.zip" into some folder on your first host
2) in start-locator.sh change the IPs of locators to the values of your host1
and host2
"--locators=10.50.3.38[20236],10.50.3.14[20236]"
3) in start-server.sh
"locators=10.50.3.38[20236],10.50.3.14[20236]" change the IPs of locators to
the values of your host1 and host2
4) do the bullets 1)-4) for host2, the folder where you unzip the file should
be the same as on the first host
Test running:
---------------
1) rm -rf {locator0,server1}
2) run ./start-server.sh on host1
3) observe in the server logs, server1/cacheserver.log:
[info 2017/06/06 18:15:16.387 MSK host1-server-1 <main> tid=0x1] Starting
membership services
[info 2017/06/06 18:15:16.504 MSK host1-server-1 <main> tid=0x1] JGroups
channel created (took 117ms)
[info 2017/06/06 18:15:16.518 MSK host1-server-1 <main> tid=0x1] GemFire P2P
Listener started on /10.50.3.38:38056
[info 2017/06/06 18:15:16.520 MSK host1-server-1 <Geode Failure Detection
Server thread 0> tid=0x1d] Started failure detection server thread on
/10.50.3.38:44771.
[info 2017/06/06 18:15:16.547 MSK host1-server-1 <main> tid=0x1] Stopping
membership services
[info 2017/06/06 18:15:16.549 MSK host1-server-1 <main> tid=0x1]
GMSHealthMonitor server socket is closed in stopServices().
[info 2017/06/06 18:15:16.549 MSK host1-server-1 <Geode Failure Detection
Server thread 0> tid=0x1d] GMSHealthMonitor server thread exiting
[info 2017/06/06 18:15:16.549 MSK host1-server-1 <main> tid=0x1]
GMSHealthMonitor serverSocketExecutor is terminated
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
