[ https://issues.apache.org/jira/browse/GEODE-3024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anthony Baker updated GEODE-3024: --------------------------------- Fix Version/s: (was: 1.2.0) 1.3.0 > race condition between server and restarted locator preparing membership views > ------------------------------------------------------------------------------ > > Key: GEODE-3024 > URL: https://issues.apache.org/jira/browse/GEODE-3024 > Project: Geode > Issue Type: Bug > Components: membership > Reporter: Bruce Schuchardt > Fix For: 1.3.0 > > > 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. -- This message was sent by Atlassian JIRA (v6.4.14#64029)