[jira] [Updated] (GEODE-3153) Client receives duplicate events during rolling upgrade

["Anthony Baker (JIRA)" <ji...@apache.org>]

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

Anthony Baker updated GEODE-3153:
---------------------------------
    Fix Version/s: 1.2.0

> Client receives duplicate events during rolling upgrade
> -------------------------------------------------------
>
>                 Key: GEODE-3153
>                 URL: https://issues.apache.org/jira/browse/GEODE-3153
>             Project: Geode
>          Issue Type: Bug
>          Components: client queues
>            Reporter: Dan Smith
>             Fix For: 1.2.0
>
>
> During a rolling upgrade from 1.1 to 1.2, we see 1.1 client receive duplicate events.
> This is the scenario
> 1) 1.1 peer is doing puts
> 2) 1.1 client has registered interest, and is connected to a 1.1 server
> 3) 1.1 server is upgraded to a 1.2 server
> 4) The client may receive some of the events that are being put twice.
> Looking further, it appears that when a put goes through a 1.1 server to a 1.1 client, the member id includes a 17 byte unique id as the last part of the serialized data. When the put goes through a 1.2 server, those 17 bytes become zeros.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)