Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Won't Fix
-
1.1.1
-
None
-
None
Description
How to reproduce:
1. Run two locators on different ports on the same machine
2. Execute gfsh, connect to each locator subsequently and execute list members. You'll see both locators in spite of the fact that gfsh is connect to one of them.
3. Disable/enable network adapter emulating network connection interruption.
4. Repeat step 2. You'll see only one locator in response to list members (actually that one gfsh is connected to).
Also there are some strange messages in the logs:
[info 2017/04/11 12:19:33.627 MSK locator_41111 <unicast receiver,VLOTAREV-17591> tid=0x24] Ignoring the view View[192.168.63.58(locator_41112:16908:locator)<ec><v1>:1025|12] members: [192.168.63.58(locator_41112:16908:locator)<ec><v1>:1025] crashed: [192.168.63.58(locator_41111:18396:locator)<ec><v0>:1024] from member 192.168.63.58(:<unknown:0>)<ec><v1>:1025, which is not in my current view View[192.168.63.58(locator_41111:18396:locator)<ec><v0>:1024|2] members: [192.168.63.58(locator_41111:18396:locator)<ec><v0>:1024] crashed: [192.168.63.58(locator_41112:16908:locator)<ec><v1>:1025]
Please see attached the full content of locator's working directories and screenshot of gfsh commands.
