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

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.4.9, 3.5.12
    • Component/s: Replication
    • Labels:
    • Backwards Compatibility:
      Fully Compatible
    • Backport Completed:
    • Sprint:
      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

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-23326 applyOps should use a single WriteUnitOfWork where possible

          • Blocker - P1 - Blocks development and/or testing work, production could not run.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-28594 non-atomic applyOps should log each individual op

          • Major - P3 - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-29874 Two Phase Drops: dropDatabase does not work with applyOps

          • Major - P3 - Major loss of function.
          • Closed

          New Feature - A new feature of the product, which has yet to be developed. SERVER-7452 Add an upsert flag to the applyOps command

          • Major - P3 - Major loss of function.
          • Closed

          New Feature - A new feature of the product, which has yet to be developed. SERVER-23892 Do periodic replicated writes every 10 seconds while idle (for maxStalenessMS)

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-29224 Move applyOps out of db/catalog/ and into db/repl/oplog

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. TOOLS-1886 oplog restore triggers server log warnings about atomic operations with timestamps

          • Major - P3 - Major loss of function.
          • Accepted

          Task - A task that needs to be done. SERVER-43458 Complete TODO listed in SERVER-29802

          • Major - P3 - Major loss of function.
          • Open

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-30536 disallow applyOps non-atomic mode when preCondition flag is used

          • Major - P3 - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-30554 relax locking mode in applyOps when applying CRUD-only ops non-atomically

          • Major - P3 - Major loss of function.
          • Closed

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                15 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: