[GEODE-9704] When durable clients recovers, it sends "ready for event" signal before register for interest, this might cause problem for caching_proxy regions

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.15.0
• Fix Version/s: 1.15.0
• Component/s: regions
• Labels: GeodeOperationAPI blocks-1.15.0 pull-request-available
• Assignee: Mark Hanson
• Reporter: Jinmei Liao
• Created: 08/Oct/21 21:39
• Updated: 22/Jun/22 20:46
• Resolved: 11/Apr/22 16:40

Description

This is the old Geode behavior, but may or may not be the correct behavior.

When durable clients recovers, there is a queueTimer thread that runs `QueueManagerImp.recoverPrimary` method,  it 

• makes new connection to server

• sends readyForEvents (which will cause the server to start sending the queued events)
• recovers interest
    - clears the region of keys of interest
    - re-registers interest

It sends readyForEvents before it clears region of keys of interest, if server sends some events of those keys in between, it will clear them, thus it seems to the user that the client region doesn't have those keys. 

 

Run geode-core distributedTest AuthExpirationDUnitTest.registeredInterest_slowReAuth_policyKeys_durableClient(), change the InterestResultPolicy to NONE, you would see the test would fail occasionally, Adding sleep code in QueueManagerImp.recoverPrimary between `createNewPrimary` and `recoverInterest` would make the test fail more consistently.

Issue Links

• relates to: GEODE-9749 CI failure: AuthExpirationDUnitTest sees EntryDestroyedException
• links to: GitHub Pull Request #7258
• links to: GitHub Pull Request #7442