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

Oplog application skips applying entries for collections not restored

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 6.0.0-rc0
    • None
    • None
    • None
    • Fully Compatible
    • Execution Team 2022-02-21, Execution Team 2022-03-07, Execution Team 2022-03-21

    Description

      When the node is restarted to replay all of the oplog entries up to the desired point-in-time, the oplog application will need to skip applying entries for collections not restored. An applyOps oplog entry can contain multiple oplog entries referencing multiple collections. This is how committed multi-document transactions are structured. Oplog entries on collections not restored will need to be skipped. The same needs to be done when foreign oplog entries are inserted.

      Attachments

        Activity

          People

            matt.kneiser@mongodb.com Matt Kneiser
            gregory.wlodarek@mongodb.com Gregory Wlodarek
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: