[
https://issues.apache.org/jira/browse/GEODE-9704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17432151#comment-17432151
]
Anilkumar Gingade commented on GEODE-9704:
------------------------------------------
I believe it should not be treated as a blocker for 1.15 release; but it is an
issue that needs to be addressed.
This behavior is existing from a long time.
This surfaces only when the result policy is NONE. There should not be any data
mismatch as there is no data pulled from server; any subsequent call will fetch
the data/value from server. When the test (specified in the ticket) is run its
validating with the region size, where it was seeing unexpected region size not
comparing the data between the client and server.
> 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
> Affects Versions: 1.15.0
> Reporter: Jinmei Liao
> Priority: Major
> Labels: GeodeOperationAPI, blocks-1.15.0
>
> 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_policyKey_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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
