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

Recover to common point on rollback instead of stable timestamp

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Replication, Storage
    • None
    • Storage Engines
    • 0

    Description

      Once we allow PIT reads on secondaries within previous batches, we should be able to simply recover to the common point on rollback instead of recovering to the stable timestamp and replaying the oplog to the common point. This will make rollback even faster and easier to understand. The recovery code can then only be used for startup recovery.

      Attachments

        Activity

          People

            backlog-server-storage-engines Backlog - Storage Engines Team
            judah.schvimer@mongodb.com Judah Schvimer
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated: