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

Use earlier oplog entry if recovery timestamp cannot be found in oplog

    XMLWordPrintable

    Details

    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v5.0
    • Sprint:
      Repl 2021-05-31, Repl 2021-06-14
    • Linked BF Score:
      121

      Description

      During recovery, we assume that the oplogApplicationStartPoint exists in the oplog.

      The oplogApplicationStartPoint derives from the stable timestamp, which is not guaranteed to be in the oplog. If the stable timestamp was greater than the oplogTruncateAfterPoint, then we move this point back to the truncate after point, which is guaranteed to be in the oplog. However, if the stable timestamp is less than the oplogTruncateAfterPoint, we don't do anything to fix the oplogApplicationStartPoint.

      Because of SERVER-51158, we guarantee that an oplog entry less than or equal to the stable timestamp exists in the oplog, so we should move the oplogApplicationStartPoint back to that oplog entry.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              vesselina.ratcheva Vesselina Ratcheva
              Reporter:
              samy.lanka Samyukta Lanka
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: