You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Hale Bales (Jira)" <ji...@apache.org> on 2022/01/20 21:45:00 UTC

[jira] [Updated] (GEODE-9640) When cluster shut down completely and restarted, new operations may be lost on client

     [ https://issues.apache.org/jira/browse/GEODE-9640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hale Bales updated GEODE-9640:
------------------------------
    Labels: GeodeOperationAPI pull-request-available  (was: GeodeOperationAPI needsTriage pull-request-available)

> 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, pull-request-available
>             Fix For: 1.12.5, 1.13.5, 1.14.1, 1.15.0
>
>
> 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.20.1#820001)