Recover to common point on rollback instead of stable timestamp

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication, Storage
    • None
    • Storage Engines
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              [DO NOT USE] Backlog - Storage Engines Team
              Reporter:
              Judah Schvimer
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated: