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

Introduce better concurrency control around setting LSID on OperationContext

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Fully Compatible
    • Service Arch 2022-11-14, Service Arch 2022-11-28, Service Arch 2022-12-12
    • 11

      Currently, readers such as killSessionsLocalKillOps will take the client lock, but writers will not (one example of many). Since the value of the LSID is not atomic, this is not a thread-safe access model.

            Assignee:
            amirsaman.memaripour@mongodb.com Amirsaman Memaripour
            Reporter:
            vesselina.ratcheva@mongodb.com Vesselina Ratcheva (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: