Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
When a locator is restarted & recovers from disk it will try to take over the role of membership coordinator for the cluster if it finds the current coordinator is a cache server. If the cache server is in the process of sending out a new view it may get into a race with the locator in sending out view preparation messages.
The locator will send out a view-prep message and the server will also send one. Responses to the view-prep message will include the conflicting view and each of the two processes will create a new view and send it out. This repeats ad-infinitum.
This problem was observed in a system that was shutting down at the same time a locator was being restarted.