Investigate changes in SPM-3828: Make mutex types observable

XMLWordPrintableJSON

    • Type: Investigation
    • Resolution: Won't Do
    • Priority: Major - P3
    • No version
    • Affects Version/s: None
    • Component/s: None
    • None
    • Not Needed
    • Developer Tools

      Original Downstream Change Summary

      There will be a new section in serverStatus that tracks mutex contentions for a subset of service-level locks.

      Description of Linked Ticket

      Epic Summary

      Summary

      Track the number of contended mutex acquisitions and report that to external observers (e.g. through FTDC metrics). Additionally, report individual mutex metrics for special instances marked by MongoDB engineers (e.g. the replication coordinator mutex). Collecting and reporting these metrics should have no performance impact on the happy path, and minimal cost on acquiring a contended mutex.

      Motivation

      The primary goal is to make an observable mutex type with negligible performance overhead to address the requirements specified in SERVER-90745 and similar tickets. The diagnostics should help TSEs and server engineers identify contended mutex acquisitions in testing and production.

      Documentation

      Product Description
      Scope
      Technical Design
      Docs Update

              Assignee:
              Unassigned
              Reporter:
              Backlog - Core Eng Program Management Team
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: