You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Kirill Tkalenko (Jira)" <ji...@apache.org> on 2025/02/25 07:57:00 UTC
[jira] [Resolved] (IGNITE-20166) Metastorage Compaction
[ https://issues.apache.org/jira/browse/IGNITE-20166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kirill Tkalenko resolved IGNITE-20166.
--------------------------------------
Resolution: Fixed
> Metastorage Compaction
> ----------------------
>
> Key: IGNITE-20166
> URL: https://issues.apache.org/jira/browse/IGNITE-20166
> Project: Ignite
> Issue Type: Epic
> Reporter: Sergey Chugunov
> Priority: Major
> Labels: ignite-3, important
> Fix For: 3.1
>
>
> General logic of metastorage is that it supports multiple versions for the same key corresponding to different timestamps.
> At the same time there is a concept of a low watermark - a moment in time when all timestamps falling below that mark become obsolete and can be pruned from Metastorage.
> We need to implement a mechanism to compact Metastorage to remove obsolete keys. At the same time some components may rely on availability of history of key's versions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)