[
https://issues.apache.org/jira/browse/GEODE-10287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17539627#comment-17539627
]
Jinmei Liao commented on GEODE-10287:
-------------------------------------
For a closed distAdvisor, the call to the `forceNewMembershipVersion` will do
something since it's calling `
operationMonitor.forceNewMembershipVersion();`, the operationMonitor is not
closed, so it will increment the `
previousVersionOpCount`, this prevents the `waitForCurrentOperations` to wait
if the distAdvisor is not closed.
> DistributedRegion.distributedRegionCleanup logic looks wrong
> ------------------------------------------------------------
>
> Key: GEODE-10287
> URL: https://issues.apache.org/jira/browse/GEODE-10287
> Project: Geode
> Issue Type: Bug
> Components: core
> Reporter: Darrel Schneider
> Assignee: Jinmei Liao
> Priority: Major
>
> DistributedRegion.distributedRegionCleanup does this: distAdvisor.close().
> Then a few lines later it calls "waitForCurrentOperations()". But
> waitForCurrentOperations uses the closed distAdvisor. Maybe it is okay to
> uses a closed distAdvisor but it seems better to call wait first and then
> close distAdvisor.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
