jchen21 commented on a change in pull request #5823:
URL: https://github.com/apache/geode/pull/5823#discussion_r539778832
##########
File path:
geode-core/src/main/java/org/apache/geode/internal/cache/AbstractRegionMap.java
##########
@@ -1282,14 +1282,18 @@ public boolean invalidate(EntryEventImpl event, boolean
invokeCallbacks, boolean
DiskRegion dr = owner.getDiskRegion();
boolean ownerIsInitialized = owner.isInitialized();
+ // lock before waitForIndexInit so that we should wait
+ // till a concurrent clear to finish
+ lockForCacheModification(owner, event);
Review comment:
Thanks @agingade ! This is exactly what I was looking for. Your comment
is automatically logged in the JIRA, so we have the context in JIRA now.
Looking at the code change of #44431 and #45699, where `waitForIndexInit()` and
`lockForCacheModification()` are introduced respectively, I don't see any side
effect of swapping the order of them. So I expect it should be good to fix this
hang, as long as Darrel's concern is addressed.
----------------------------------------------------------------
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:
[email protected]
