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

Kirill Tkalenko updated IGNITE-23281:
-------------------------------------
    Fix Version/s: 3.0

> 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
>             Fix For: 3.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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)

Reply via email to