Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-70296

Serialize concurrent access to CurOp dataThroughputLastSecond and dataThroughputAverage metrics

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 6.2.0-rc0
    • None
    • None
    • None
    • Fully Compatible
    • ALL
    • Execution Team 2022-10-17
    • 15

    Description

      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.

      Attachments

        Activity

          People

            gregory.wlodarek@mongodb.com Gregory Wlodarek
            gregory.wlodarek@mongodb.com Gregory Wlodarek
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: