Hi All, I would like to check one thing related to .dat files existing on the machines from where locator have been started.
We have multiple machines connecting distributed system which run clients, servers and locators. On setups where locator services have been started we discover that current membership view is persisted in locator6061.dat file. And once distributed system is restarted, we see that recovery process from these files is taking place. Is there some way to say Geode to omit this and don't use persisted files during startup? Actually we reach this by removing these files when whole distributed system shutdown. Afterwards following occurs in locator log file once first locator is started: [info 2017/04/27 22:03:32.042 AMT <Thread-0> tid=0x9] Starting peer location for Distribution Locator on Replica[0] [info 2017/04/27 22:03:32.045 AMT <Thread-0> tid=0x9] Starting Distribution Locator on Replica[0] [info 2017/04/27 22:03:32.046 AMT <Thread-0> tid=0x9] Locator was created at Thu Apr 27 22:03:32 AMT 2017 [info 2017/04/27 22:03:32.047 AMT <Thread-0> tid=0x9] Listening on port 6061 bound on address 0.0.0.0/0.0.0.0 [info 2017/04/27 22:03:32.048 AMT <Thread-0> tid=0x9] GemFire peer location service starting. Other locators: Replica[6061],Master[6061] Locators preferred as coordinators: false Network partition detection enabled: false View persistence file: locator6061view.dat [info 2017/04/27 22:03:32.049 AMT <Thread-0> tid=0x9] Peer locator attempting to recover from /Replica:6061 [info 2017/04/27 22:03:32.692 AMT <Thread-0> tid=0x9] Peer locator was unable to recover state from this locator [info 2017/04/27 22:03:32.692 AMT <Thread-0> tid=0x9] Peer locator attempting to recover from /Master:6061 [info 2017/04/27 22:03:32.694 AMT <Thread-0> tid=0x9] Peer locator was unable to recover state from this locator [info 2017/04/27 22:03:32.694 AMT <Thread-0> tid=0x9] Peer locator recovering from /usr/lib/vmware-vcops/common/bin/locator6061view.dat [info 2017/04/27 22:03:32.705 AMT <Thread-0> tid=0x9] Peer locator initial membership is View[Replica(7553:locator)<ec><v0>:20002|6] members: [Replica(7553:locator)<ec><v0>:20002, Master(8188:locator)<ec><v1>:20002] shutdown: [Data1(DNODE:4634)<ec><v2>:10002] [info 2017/04/27 22:03:32.706 AMT <Thread-0> tid=0x9] Starting distributed system Then new view is created on new member joins and everything works as expected. So the question is whether removing of these files could have any side effect? Is it harmless operation and with these removals we just force Geode to do view creation without any cached date? Thanks, Vahram.
