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

recoverFromOplogUpTo should not invariant if there are no oplog entries to apply between the given range

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.2.4, 4.3.4
    • None
    • Replication
    • None
    • Fully Compatible
    • ALL
    • v4.2
    • Execution Team 2020-02-10
    • 0

    Description

      recoverFromOplogUpTo was added as part of the queryable project and after integration testing with cloud backup, we missed an edge case where there are no oplog entries to apply between the given range, but the oplog entry at the start point is present, which we skip. Because of that, later on, we try to set the applied through point to the null timestamp causing an invariant.

      Attachments

        Activity

          People

            gregory.wlodarek@mongodb.com Gregory Wlodarek
            gregory.wlodarek@mongodb.com Gregory Wlodarek
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: