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

Biggie oplog visibility is not correct

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.7.0
    • None
    • None
    • None
    • Fully Compatible
    • Execution Team 2020-07-13, Execution Team 2020-07-27

    Description

      New uncommited inserts on the oplog happen with RecordIds that are lower than the currently known lowest uncommitted insert.

      This leads to cursors on the oplog throwing CappedPositionLost when entries that they previously saw become hidden.

      This makes replication broken on the Biggie storage engine.

      Attachments

        Activity

          People

            henrik.edin@mongodb.com Henrik Edin
            henrik.edin@mongodb.com Henrik Edin
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: