[ https://issues.apache.org/jira/browse/GEODE-9640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17427367#comment-17427367 ]
ASF subversion and git services commented on GEODE-9640: -------------------------------------------------------- Commit 473f287c6ee4d5804b2c8a90ef443ce1b4f5921a in geode's branch refs/heads/support/1.14 from Eric Shu [ https://gitbox.apache.org/repos/asf?p=geode.git;h=473f287 ] GEODE-9640: Initiate threadId in EventID. (#6905) * This is to make sure a new EventID can be generated after server restarted after a whole cluster is shut down. * Wrap around original threadID before it interferes with bulkOp or wan generated threadID. (cherry picked from commit 4b3c49e788157df94f7d3e4b455adb7a6eaef96b) > When cluster shut down completely and restarted, new operations may be lost > on client > ------------------------------------------------------------------------------------- > > Key: GEODE-9640 > URL: https://issues.apache.org/jira/browse/GEODE-9640 > Project: Geode > Issue Type: Bug > Components: client/server > Reporter: Eric Shu > Assignee: Eric Shu > Priority: Major > Labels: GeodeOperationAPI, needsTriage, pull-request-available > > In Geode, client keeps track of events received based on EventID. If > duplicate events received from server, they are thrown away. > The current EventID takes parts of membership ID information, and it seems > not adequate enough if whole cluster is down. (The coordinator is down and > member viewId will start from 0 again.) This can lead to same event ids are > generated, and cause client miss CQ events, etc. -- This message was sent by Atlassian Jira (v8.3.4#803005)