[
https://issues.apache.org/jira/browse/GEODE-8790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17260947#comment-17260947
]
ASF subversion and git services commented on GEODE-8790:
--------------------------------------------------------
Commit 2049768ba20aa44a587612f0d328eeaf6e9b1ad8 in geode's branch
refs/heads/develop from Louis Jacome
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=2049768 ]
GEODE-8790: Evicted entries sometimes remain in region map (#5851)
- Modifies regionMapDestroy.retryRemoveWithTombstone to handle case where an
evicted entry was left in the region map when concurrency checks is enabled
> Evicted entries sometimes remain in region map
> ----------------------------------------------
>
> Key: GEODE-8790
> URL: https://issues.apache.org/jira/browse/GEODE-8790
> Project: Geode
> Issue Type: Bug
> Components: eviction
> Affects Versions: 1.1.0, 1.14.0
> Reporter: Louis R. Jacome
> Assignee: Louis R. Jacome
> Priority: Major
> Labels: blocks-1.14.0, pull-request-available
>
> Sometimes an entry set for eviction will remain in the region map after
> falling into an unhandled case in RegionMapDestroy.retryRemoveWithTombstone.
> When testing the LRU capacity of a region, we create many entries beyond the
> LRU capacity, causing evictions. We sometimes run into a case where two
> threads compete to remove the same entry. One thread succeeds and removes it
> from the region map, while the other thread, in removal progress, will create
> a temporary entry in the map that does not get properly removed/handled.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
