You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Anilkumar Gingade (JIRA)" <ji...@apache.org> on 2018/03/22 22:06:00 UTC
[jira] [Updated] (GEODE-4245) Support for Tombstone GC setting at
region level
[ https://issues.apache.org/jira/browse/GEODE-4245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anilkumar Gingade updated GEODE-4245:
-------------------------------------
Summary: Support for Tombstone GC setting at region level (was: Users would like a parameter to limit the number of tombstones to purge every Tombstone GC)
> Support for Tombstone GC setting at region level
> ------------------------------------------------
>
> Key: GEODE-4245
> URL: https://issues.apache.org/jira/browse/GEODE-4245
> Project: Geode
> Issue Type: Improvement
> Components: regions
> Reporter: Fred Krone
> Priority: Major
> Labels: geode-150
>
> Sometimes there is an issue which makes transactions longer to commit by competing with Tombstone GC.
> A workaround is to reduce the number of data entries to be removed at once in their system. However, it's a slightly undesirable workaround involving un-wanting modification with their application. It could be handled by adding a parameter with Tombstone GC feature.
> limit the number of tombstones to purge every Tombstone GCs
> Or..
> set the maximum execution time for every Tombstone GCs
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)