SERVER-134803Open
Logging under mutex stalled mongod for the 4 seconds
`ReplicationCoordinatorImpl` emits log records *{*}while holding `_mutex`{*}*, and the logv2 sink serialises on its own mutex *{*}across the backend write{*}*. A log consumer that is slow or blocked therefore does not merely delay logging: it holds `_mutex` for the full duration of the write, stalling every other user of that mutex — inbound `replSetHeartbeat`, the `oplog` `serverStatus` section, and the heartbeat scheduler itself. The BF-45880 is a reproduction of the problem - mongod g