You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Andrey Mashenkov (Jira)" <ji...@apache.org> on 2022/12/22 12:51:00 UTC

[jira] [Updated] (IGNITE-18441) Fix busylock usage in MetastorageManager

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

Andrey Mashenkov updated IGNITE-18441:
--------------------------------------
    Description: 
As for now we chain operation future to a metastorage init future under busy lock, but operation futures completion is not wrapped with busy lock.


  was:
As for now we chain operation future to a metastorage init future under busy lock,
but operation future completion is not covered with busy lock.


> Fix busylock usage in MetastorageManager
> ----------------------------------------
>
>                 Key: IGNITE-18441
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18441
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Andrey Mashenkov
>            Priority: Major
>              Labels: ignite-3
>
> As for now we chain operation future to a metastorage init future under busy lock, but operation futures completion is not wrapped with busy lock.



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