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

Concurrent access of waitForWriteConcernDurationMillis in OpDebug

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 7.1.0-rc0
    • None
    • None
    • None
    • Fully Compatible
    • ALL
    • Repl 2023-05-01, Repl 2023-05-15
    • 35

    Description

      Field waitForWriteConcernDurationMillis in OpDebug is able to be accessed twice. Once by reportState (for reporting currentOp) and once when finishing waiting for write concern. The solution here should be to use another atomic variable to keep track of current duration in ticks and then only convert to and use the millis duration for use in slow query

      Attachments

        Activity

          People

            sean.zimmerman@mongodb.com Sean Zimmerman
            sean.zimmerman@mongodb.com Sean Zimmerman
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: