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

Data race in writeConflictRetryLimit server parameter

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication
    • Fully Compatible
    • ALL
    • v8.1, v8.0
    • Repl 2025-03-31
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Tsan detected the race condition on the server parameter. It is being declared non-atomic, but being unprotectedly read here,  and being written (under mutex) via 
      IDLServerParameterWithStorage wrapping class. To get rid of the race condition consider declaring the parameter atomic in its idl spec.
      Note: storage_wrapper class used inside  IDLServerParameterWithStorage to wrap server parameter access has a template specialization for atomic types that allows to avoid nested atomicity and prevent additional overhead.

            Assignee:
            brad.cater@mongodb.com Brad Cater
            Reporter:
            solomon.lifshits@mongodb.com Solomon Lifshits
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: