Data race in waitForReadConcernImpl

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 7.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • Repl 2023-12-25, Repl 2024-01-08
    • 120
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When setting the cached oplog Collection pointer in local_oplog_info we do so under the protection of the global lock. When we read the pointer we are not under lock which can lead to a data race.

            Assignee:
            Sean Zimmerman
            Reporter:
            Sean Zimmerman
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: