The locator view file exists to allow locators to be bounced without
shutting down the rest of the cluster. On startup a locator will try to
find the current membership coordinator of the cluster from an existing
locator and join the system using that information. If there is no
existing locator that knows who the coordinator might be then the new
locator will try to find the coordinator using the membership "view"
that is stored in the view file. If there is no view file the locator
will not be able to join the existing cluster.
If you've done a full shutdown of the cluster it is safe to delete the
locator*view.dat files.
When there is no .dat file the locators will use a concurrent-startup
algorithm to form a unified system.
On 6/8/17 7:48 AM, Anton Mironenko wrote:
Hello,
We found out that if we delete “locator*view.dat” before starting a
locator,
It fixes the first part of the issue
https://issues.apache.org/jira/browse/GEODE-3003
“Geode doesn't start after cluster restart when using
cluster-configuration”
“The second start goes wrong: the locator on the first host always
doesn't join the rest of the cluster with the error in the locator log:
"Region /_ConfigurationRegion has potentially stale data. It is
waiting for another member to recover the latest data."”
What is a side effect of deleting the file
"locator0/locator*view.dat"? What functionality do we lose?
A use case with some example would be great.
Anton Mironenko
This message and the information contained herein is proprietary and
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer
