It is possible for getLocalOplogCollection in oplog.cpp to overwrite the CurOp namespace for a user operation. This can lead to incorrect namespace in diagnostics for the given operation as well as writing of any system.profile entry to the local rather than the user database.
This occurs when:
- A user operation triggers collection creation
- The oplog.cpp _localOplogCollection Collection* has not been set to point to the local.oplog.rs collection
- OldClientContext creation (used to obtain the oplog.rs handle) sets the OperationContext to the local.oplog.rs namespace (via CurOp::enter_inlock() call).