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

non-atomic applyOps should log each individual op

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.4.14, 3.5.8
    • Storage
    • None
    • Fully Compatible
    • ALL
    • v3.4
    • Storage 2017-05-08, Storage 2017-05-29

    Description

      Non-atomic applyOps commands should not suppress normal oplog generation and then record a single applyOps command in the oplog, but instead log the individual commands.

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-19768 Failed applyOps command does not create an oplog entry even with some successful writes

          • Critical - P2 - Crashes, loss of data, severe memory leak.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-36944 applyOps does not permit unknown field names when creating a v:1 index

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-37333 [3.4] applyOps does not validate background index spec for system.indexes inserts

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

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-29802 Non-atomic applyOps command should not take out a global exclusive lock

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

          Activity

            People

              maria.vankeulen@mongodb.com Maria van Keulen
              geert.bosch@mongodb.com Geert Bosch
              Votes:
              0 Vote for this issue
              Watchers:
              15 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: