[GEODE-3153] Client receives duplicate events during rolling upgrade

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.2.0
• Component/s: client queues
• Assignee: Unassigned
• Reporter: Dan Smith
• Created: 29/Jun/17 18:29
• Updated: 17/Jul/17 18:06
• Resolved: 11/Jul/17 19:22

Description

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.