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/09/28 10:42:00 UTC

[jira] [Assigned] (IGNITE-23281) KeyValueStorage#compact should not hold a write lock

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

Kirill Tkalenko reassigned IGNITE-23281:
----------------------------------------

    Assignee: Kirill Tkalenko

> KeyValueStorage#compact should not hold a write lock
> ----------------------------------------------------
>
>                 Key: IGNITE-23281
>                 URL: https://issues.apache.org/jira/browse/IGNITE-23281
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Kirill Tkalenko
>            Assignee: Kirill Tkalenko
>            Priority: Major
>              Labels: ignite-3
>
> At the moment, the implementation of *org.apache.ignite.internal.metastorage.server.KeyValueStorage#compact* holds a цкшеу lock, because of which we can hang reading and writing to the metastorage for a long time until the metastorage compaction ends.
> Which is critical for us, since the internal components actively use the metastorage.
> I also think that we don’t need to rely on a timestamp, but on revision.



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