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

hold write lock between finishing a batch and updating the oplog

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • 2.7.8
    • 2.4.3
    • Performance, Replication
    • None
    • Fully Compatible

    Description

      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.

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: