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

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.2.4, 4.3.4
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • v4.2
    • Execution Team 2020-02-10

      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.

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

              Created:
              Updated:
              Resolved: