|
SERVER-69893 proposed a new LockManager lock type that represents a mutex lockable by name. Using that would be appropriate for this case; however, current decision is not to introduce that new LockManager type.
On master, we believe there is actually no need for BalancerStatsRegistry to use that RESOURCE_MUTEX because the only usage of the "weak" variant of ScopedRangeDeleterLock is here, and I believe it would enough to lock the rangeDeleter collection in MODE_IX, because:
(1) It already conflicts with the "strong" variant.
(2) The work currently done under that lock does not need to serialize on a particular collection uuid.
On v6.0, the situation is more complex, since the weak variant is used on the FCV upgrade procedure. More analysis is needed to find a solution.
(cc allison.easton@mongodb.com)
|