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

During recovery replicas should truncate the oplog to start position of the failed batch

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.2.0-rc0
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • RPL A (10/09/15), Repl B (10/30/15)
    • 0

      We need to truncate the oplog to the start of the active/failed oplog batch when we recover from a failed batch.

      While database operations are idempotent, the inserting of the oplog entries are not, and need to be removed (via truncate) before we apply again, much like rollback does.

            Assignee:
            scotthernandez Scott Hernandez (Inactive)
            Reporter:
            scotthernandez Scott Hernandez (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: