[
https://issues.apache.org/jira/browse/GEODE-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16068764#comment-16068764
]
Dan Smith commented on GEODE-3153:
----------------------------------
I created a test that demonstrates the member id issue and put it here -
https://github.com/upthewaterspout/incubator-geode/commit/6448367784fb10354bd0fce71eab1eaee270b1e7
> 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
>
> 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)
