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

Remove assertion that checks whether the last applied oplog entry has the same timestamp as the requested recover timestamp in recoverFromOplogUpTo

    XMLWordPrintableJSON

Details

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

    Description

      This was originally implemented for queryable backup, but for sharded clusters, a majority commit point is used as the recovery timestamp. Not all shards may have an oplog entry at the majority commit point, however, and the code expects an oplog entry to be there at the passed in recovery timestamp.

      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: