ExportXMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication, Replication - Oplog and Recovery
    • ALL
    • Show
      BRIEF.md
    • QE 2026-09-15, Repl 2026-10-12, Repl 2026-10-26, Repl 2026-11-09, Repl 2026-11-23
    • 0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      `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 got stuck for the 4 seconds because of it.

            Assignee:
            Brad Cater
            Reporter:
            Vadim Piven
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: