[IGNITE-18441] Fix busylock usage in MetastorageManager

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Labels: ignite-3
• Epic Link: Grid start-stop scenarios
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Unassigned
• Reporter: Andrey Mashenkov
• Created: 21/Dec/22 11:00
• Updated: 23/Dec/22 20:27

Description

Motivation:

We are using a busy lock to avoid invocation of a manager's method when the manager has already stopped. The same manner the lock should work in MetastorageManager, but because it has a specific future (metaStorageSvcFut) that completes when a metasorage RAFT group starts. We chain operation future to metaStorageSvcFut under busy lock, but operation future's completion is not wrapped with busy lock.

Definition of done:

All code invocation in the metastorage manager should lead to NODE_STOPPING_ERR when the manager is stopped, whatever it is during chanting of futures or code in the future listener.

Implementation notes:

Wrap all action that executed after metaStorageSvcFut in IgniteUtils#inBusyLock(lock, supplier)

Issue Links

• is cloned by: IGNITE-18446 Fix busylock usage in ClusterManagementGroupManager
• relates to: IGNITE-15389 org.apache.ignite.internal.metastorage.client.CursorImpl has potential deadlock inside