[IGNITE-18446] Fix busylock usage in ClusterManagementGroupManager

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0
• Labels: ignite-3
• Epic Link: Grid start-stop scenarios
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Semyon Danilov
• Reporter: Andrey Mashenkov
• Reviewer: Aleksandr Polovtsev
• Created: 22/Dec/22 13:02
• Updated: 04/Sep/24 16:19
• Resolved: 26/Jan/23 16:53

Description

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).

Issue Links

• is a clone of: IGNITE-18441 Fix busylock usage in MetastorageManager
• is cloned by: IGNITE-18447 Hanging in RebalanceRaftGroupEventsListener
• links to: GitHub Pull Request #1579