Biggie oplog visibility is not correct

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.7.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • Execution Team 2020-07-13, Execution Team 2020-07-27
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Henrik Edin
            Reporter:
            Henrik Edin
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: