This is problematic because the profile command on mongos uses a LockerNoop and CollectionCatalog::write(). SERVER-58736 introduced an optimization to skip copying the collection catalog on write if the exclusive global lock is held. But the usage of LockerNoop in the profile command breaks this assumption given that isW() always returns true.
- related to
-
SERVER-58736 Avoid quadratic behavior in rollback with many collections
- Closed
-
SERVER-59618 Avoid using LockerNoop outside of unit tests
- Closed
-
SERVER-60229 lock manager for mongos
- Closed