[GEODE-8926] CQ events can be missed while executing with initial results simultaneously with transactions

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.12.2, 1.13.3, 1.14.0, 1.15.0
• Component/s: cq
• Labels: blocks-1.14.0​ pull-request-available
• Assignee: Eric Shu
• Reporter: Barrett Oglesby
• Created: 08/Feb/21 18:08
• Updated: 24/Jun/21 23:35
• Resolved: 07/Apr/21 17:26

Description

In this case, the event is not in either the initial results or received in the CqListener.

A test that shows the behavior is:

• 2 servers with:
• a root PR
• a colocated child PR

In a client, asynchronously:

• start a transaction that:
• does N puts into the root PR
• does 1 put into the child PR
• commit the transaction

In the client:

create N CQs with initial results with: 'select * from /childPR'

When the test succeeds, all the CQs either get the 1 event in their initial results or in their CqListener.

When the test fails, one or more CQs don't see the event either way.

Issue Links

• links to: GitHub Pull Request #6227
• links to: GitHub Pull Request #6232
• links to: GitHub Pull Request #6277