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

hold write lock between finishing a batch and updating the oplog

    • Type: Icon: Improvement Improvement
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 2.7.8
    • Affects Version/s: 2.4.3
    • Component/s: Performance, Replication
    • None
    • Fully Compatible
    • None
    • 0
    • None
    • None
    • None
    • None
    • None
    • None

      Right now we drop the write lock between finishing a batch and updating the oplog (and notifying upstream that we've applied ops).
      This allows queued readers to run, and will delay our reporting of our progress upstream. This may in turn needlessly delay write concern getLastError calls on the primary.

            Assignee:
            Unassigned Unassigned
            Reporter:
            milkie@mongodb.com Eric Milkie
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: