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

Biggie oplog visibility is not correct

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.7.0
    • Component/s: None
    • Labels:
      None

      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

            Assignee:
            henrik.edin Henrik Edin
            Reporter:
            henrik.edin Henrik Edin
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: