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

Replication should ensure that minValid is hit exactly

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Replication
    • None
    • Replication

    Description

      Currently replication just checks that we become >= minValid before becoming secondary, without checking that we actually applied the exact minValid optime. This can lead to an undetected corruption if there was an upstream rollback between the time we fetched documents that caused us to set minValid and the time we fetched the oplog entry that is >= minValid. Note that if we detect this state, the only possible fix is to do a full resync.

      Attachments

        Activity

          People

            backlog-server-repl Backlog - Replication Team
            mathias@mongodb.com Mathias Stearn
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: