Serialize concurrent access to CurOp dataThroughputLastSecond and dataThroughputAverage metrics

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 6.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • Execution Team 2022-10-17
    • 15
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      CommonProcessInterface::getCurrentOps() already locks the client before retrieving the CurOp report. The throttle cursor does not. We should lock the client in the throttle cursor prior to updating CurOp.

            Assignee:
            Gregory Wlodarek
            Reporter:
            Gregory Wlodarek
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: