Investigate using AtomicLockStats over SingleThreadedLockStats in lock_state.h

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 5.2.0, 5.0.27
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • v5.0
    • Execution Team 2021-10-18
    • 35
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Operations that use the LockerImpl interface for acquiring locks are expected to call the lock/unlock methods from a single thread.

      A part of locking a lock involves incrementing the lock stats (_stats in lock_state.h). Single-threaded access to this data structure is not enforced as CurOp can access it concurrently for user reporting purposes.

      To fix TSAN build failures in this area we should investigate using AtomicLockStats over SingleThreadedLockStats.

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

              Created:
              Updated:
              Resolved: