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 13:14:00 UTC

[jira] [Created] (IGNITE-18447) Fix busylock usage in RebalanceRaftGroupEventsListener

Andrey Mashenkov created IGNITE-18447:
-----------------------------------------

             Summary: Fix busylock usage in RebalanceRaftGroupEventsListener
                 Key: IGNITE-18447
                 URL: https://issues.apache.org/jira/browse/IGNITE-18447
             Project: Ignite
          Issue Type: Bug
            Reporter: Andrey Mashenkov


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)