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

Posted to issues@ignite.apache.org by "Semyon Danilov (Jira)" <ji...@apache.org> on 2023/01/17 13:13:00 UTC

[jira] [Assigned] (IGNITE-18446) Fix busylock usage in ClusterManagementGroupManager

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

Semyon Danilov reassigned IGNITE-18446:
---------------------------------------

    Assignee: Semyon Danilov

> Fix busylock usage in ClusterManagementGroupManager
> ---------------------------------------------------
>
>                 Key: IGNITE-18446
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18446
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Andrey Mashenkov
>            Assignee: Semyon Danilov
>            Priority: Major
>              Labels: ignite-3
>
> As for now we chain operation future to a joinFuture under busy lock, but operation futures completion is not wrapped with busy lock.
> Startpoint is ClusterManagementGroup.metaStorageNodes(): in readClusterState() method we run a raft command, but raft service might not be aware of node is stopping (as well as lower level components).
> Also, raftservice has no stop() method.



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