As part of SERVER-99150 we've implemented a lock ordering checker. It detected a conflict in ReplicaSetNodeProcessInterface::getWriteSizeEstimator.

During the execution of the code we acquire the RSTL lock to check if we can write locally. This happens whenever we instantiate a DocumentSourceWriter class ($out and $merge).

However, this call may occur after having acquired the Global lock, which is always taken after having acquired the RSTL lock in the hierarchy.

As we're potentially taking the RSTL lock out of order with respect to other operations we should investigate if this can be refactored to stay in line with the other operations and avoid taking the RSTL lock altogether.