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 2024/12/05 13:16:00 UTC
[jira] [Updated] (IGNITE-23847) Add metastorage revision update notification for operations that do not update metastorage data
[ https://issues.apache.org/jira/browse/IGNITE-23847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kirill Tkalenko updated IGNITE-23847:
-------------------------------------
Reviewer: Roman Puchkovskiy
> Add metastorage revision update notification for operations that do not update metastorage data
> -----------------------------------------------------------------------------------------------
>
> Key: IGNITE-23847
> URL: https://issues.apache.org/jira/browse/IGNITE-23847
> Project: Ignite
> Issue Type: Bug
> Reporter: Kirill Tkalenko
> Assignee: Kirill Tkalenko
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I found that operations that update the metastorage revision, but do not update its data, do not notify about the revision update, so for example, the version values do not know about it.
> This can lead to errors when cleaning up version values on the compaction. For example, the last revision that the version values know about is 11, and an operation came that did nothing but updated the revision to 12, the version value was not updated, then when the metastorage compaction wants to delete everything up to revision 12, we get an error when trying to clean up the version value up to revision 12, since for the version value its last revision is 11 and it cannot be deleted.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)