[
https://issues.apache.org/jira/browse/IGNITE-18446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Semyon Danilov updated IGNITE-18446:
------------------------------------
Reviewer: Aleksandr Polovtcev
> 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
> Fix For: 3.0.0-beta2
>
> Time Spent: 3h
> Remaining Estimate: 0h
>
> 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).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
