[
https://issues.apache.org/jira/browse/GEODE-8991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17337408#comment-17337408
]
ASF subversion and git services commented on GEODE-8991:
--------------------------------------------------------
Commit 085cdb9c76faf6ec4b040b9d1e00378d95cccebe in geode-native's branch
refs/heads/develop from Blake Bender
[ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=085cdb9 ]
Revert "GEODE-8991: Implement cached region clean up (#757)" (#798)
- Consistent failures in legacy C++ test testThinClientHADistOps in CI
> Cached regions are not cleaned up whenever the connection to the cluster is
> lost
> --------------------------------------------------------------------------------
>
> Key: GEODE-8991
> URL: https://issues.apache.org/jira/browse/GEODE-8991
> Project: Geode
> Issue Type: Bug
> Components: native client
> Affects Versions: 1.15.0
> Reporter: Mario Salazar de Torres
> Assignee: Mario Salazar de Torres
> Priority: Major
> Labels: pull-request-available
>
> Under a cluster restart scenario it can't be guaranteed that all the entries
> that existed before, exist after the restart. Hence if geode-native client
> has any cached region registered it should be cleared after the connection is
> lost towards the cluster in order to ensure cache consistency.
> This is happenig in the case of the Java client, as described in this part of
> the documentation:
> [https://geode.apache.org/docs/guide/12/developing/events/how_client_server_distribution_works.html#how_client_server_distribution_works__section_928BB60066414BEB9FAA7FB3120334A3]
> However, this is not the case for the native client
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
