Client lock is no longer necessary in OplogSlotReserver

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Replication
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Since SERVER-40498, we no longer need to take the Client lock when reserving oplog slots for transactions because we are not modifying anything on the Client that could be accessed concurrently.

            Assignee:
            [DO NOT USE] Backlog - Replication Team
            Reporter:
            Louis Williams
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: