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

May fail to recover after a rollbackViaRefetch if sync source no longer has required opTime

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Replication
    • None
    • Replication
    • ALL
    • 30

    Description

      In order to reach a consistent state after doing a rollbackViaRefetch, the rollback node sets its own minValid to the top of sync source's oplog at the start of recovery. It therefore must be able to replicate and apply up to that lastApplied to complete the recovery. However, if at some point mid-recovery the necessary oplog entries are no longer in the set (either due to a rollback or an unclean shutdown), the rollback node will end up in an unrecoverable state as it may only choose a sync source that has them.

      Attachments

        Activity

          People

            backlog-server-repl Backlog - Replication Team
            vesselina.ratcheva@mongodb.com Vesselina Ratcheva (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: