geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (GEODE-4651) transactional region entry destroys do not remove from the eviction list
Date Wed, 14 Feb 2018 05:24:00 GMT


ASF subversion and git services commented on GEODE-4651:

Commit da5da792874f04b276a015f658f3a1a6a8301e4c in geode's branch refs/heads/feature/GEODE-3967
from [~dschneider]
[;h=da5da79 ]

GEODE-4651: fix transactional destroy entry leak (#1433)

When the transaction marks a region entry as no
longer being used by the transaction, it no longer
added it back to the eviction list if the entry
is removed or destroyed.

> transactional region entry destroys do not remove from the eviction list
> ------------------------------------------------------------------------
>                 Key: GEODE-4651
>                 URL:
>             Project: Geode
>          Issue Type: Bug
>          Components: eviction, transactions
>            Reporter: Darrel Schneider
>            Assignee: Darrel Schneider
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.5.0
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
> If a geode transaction destroys a region entry on a region that has eviction, then that
region entry should be available for garbage collection.
> But the transaction code adds the destroy entry back to the eviction list which can cause
the entry to not be garbage collected. In the future, if on operation is done on that region
that triggers an evict, then these destroyed region entries will be released to the garbage
collector. But if no future eviction occurs the destroyed entries will never be garbage collected.

This message was sent by Atlassian JIRA

View raw message