Update the CurOp::numYields metric to reflect global lock yields

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The CurOp::numYields counter should report the number of times an operation releases the global lock to allow other operations into the storage engine layer. Currently, it is incremented manually in various locations, making the metric inaccurate.

      This is a significant issue because our new execution control logic de-prioritizes operations based on storage engine accesses, and customers monitoring CurOp::numYields will be confused by this discrepancy.

      To fix this, the metric should be refactored to be derived from the number of times an operation is granted admission to the storage engine, which accurately reflects the number of global lock releases.

            Assignee:
            Unassigned
            Reporter:
            Pol Pinol
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: