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

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.2.4, 4.3.4
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v4.2
    • Sprint:
      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

            Assignee:
            gregory.wlodarek Gregory Wlodarek
            Reporter:
            gregory.wlodarek Gregory Wlodarek
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: