Add hash to minvalid OpTime boundaries

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • Replication
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      In the case there is a rollback after/during a failed apply batch it is possible to fetch new oplog entries with matching OpTimes but different hashes when recovering and applying the batch again – although very unlikely...

      Oplog-as-a-buffer will address this since we will always have the oplog entries locally.

            Assignee:
            [DO NOT USE] Backlog - Replication Team
            Reporter:
            Scott Hernandez (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: