Jinmei Liao created GEODE-9704:
----------------------------------
Summary: When durable clients recovers, it sends "ready for event"
signal before register for interest, this might cause problem for caching_proxy
regions
Key: GEODE-9704
URL: https://issues.apache.org/jira/browse/GEODE-9704
Project: Geode
Issue Type: Bug
Components: regions
Reporter: Jinmei Liao
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_policyNone_durableClient, but 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
