Use ObservableMutex for logging system locks

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Networking & Observability
    • Fully Compatible
    • N&O 2025-09-29, N&O 2025-10-13, N&O 2025-10-27
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The logging system acquires two locks on every log:

      https://github.com/10gen/mongo/blob/42d9b470f1fda4c928e7890080447342bc12ef35/src/mongo/logv2/composite_backend.h#L64

      https://github.com/10gen/mongo/blob/42d9b470f1fda4c928e7890080447342bc12ef35/src/mongo/logv2/ramlog.h#L154

      We should use the observable mutex for each of these, as they've been linked to production incidents that have been difficult to pinpoint.

            Assignee:
            Sergei Bazhenov
            Reporter:
            Erin McNulty
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: