[
https://issues.apache.org/jira/browse/GEODE-9704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17430681#comment-17430681
]
ASF subversion and git services commented on GEODE-9704:
--------------------------------------------------------
Commit cdfae8f8fd11f75622b5b00d168662fcffc363e5 in geode's branch
refs/heads/develop from Jinmei Liao
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=cdfae8f ]
GEODE-9749: ignore the test case that shows GEODE-9704. (#7015)
> 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)
