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

Non-atomic applyOps command should not take out a global exclusive lock

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.4.9, 3.5.12
    • Replication
    • Fully Compatible
    • Repl 2017-07-31, Repl 2017-08-21

    Description

      The applyOps command currently takes out a global exclusive lock and applies operations serially. This limits the number of operations that can be applied due to the lack of concurrency. Having applyOps (when in non-atomic mode) not take out a global lock would allow us to parallelize applyOps calls and take advantage of collection- and document-level locking.

      Attachments

        Issue Links

          Activity

            People

              benety.goh@mongodb.com Benety Goh
              steve.briskin Steve Briskin
              Votes:
              0 Vote for this issue
              Watchers:
              15 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: