[
https://issues.apache.org/jira/browse/GEODE-8991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17335854#comment-17335854
]
ASF GitHub Bot commented on GEODE-8991:
---------------------------------------
gaussianrecurrence commented on pull request #798:
URL: https://github.com/apache/geode-native/pull/798#issuecomment-829640357
Sorry this made an old IT fail. Not sure why this did not pop up before in
CI. I am looking at why the test is failing. Once solved, I'll create a new PR
for GEODE-8991
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> 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)
