You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Jakov Varenina (Jira)" <ji...@apache.org> on 2022/08/30 06:42:00 UTC

[jira] [Resolved] (GEODE-10412) Destry region command doesn't clear the region related expired tombstones

     [ https://issues.apache.org/jira/browse/GEODE-10412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jakov Varenina resolved GEODE-10412.
------------------------------------
    Fix Version/s: 1.16.0
       Resolution: Fixed

> Destry region command doesn't clear the region related expired tombstones
> -------------------------------------------------------------------------
>
>                 Key: GEODE-10412
>                 URL: https://issues.apache.org/jira/browse/GEODE-10412
>             Project: Geode
>          Issue Type: Bug
>            Reporter: Jakov Varenina
>            Assignee: Jakov Varenina
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.16.0
>
>
> Tombstones in geode are kept on two maps: expiredTombstones and tombstones (non-expired ones). When a region is destroyed, it must clear all the related expired and non-expired tombstones from memory. Due to the below code bug, expired tombstones aren't cleared when non-expired tombstones are available during the region destruction:
> {code:java}
> private boolean removeIf(Predicate<Tombstone> predicate) {      
>   return removeUnexpiredIf(predicate) || removeExpiredIf(predicate);    
> }
> {code}
> Because of the above, non-expired tombstones are never removed from memory, preventing other tombstones from being cleared. Since other tombstones never expire, the compaction is not done, and therefore the disk is filled, causing the issues.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)