[GEODE-8964] Entry created via TX putIfAbsent with null value can write incorrect data to cache

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.10.0, 1.14.0
• Fix Version/s: 1.15.0
• Component/s: client/server
• Labels: pull-request-available
• Assignee: Louis R. Jacome
• Reporter: Louis R. Jacome
• Created: 23/Feb/21 18:23
• Updated: 22/Jun/22 20:46
• Resolved: 08/Mar/21 17:05

Description

In backwards compatibility testing, an error was seen wherein a putIfAbsent with a null value was being processed by a server but interrupted by a GII with the same key. The operation was subsequently enqueued in the client's HA Region Queue as an update with a null value rather than a create with a null value – a path that's not supported – resulting in erroneous data sometimes being written to the client cache.

Issue Links

• links to: GitHub Pull Request #6053
• links to: GitHub Pull Request #6067