Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-14131

Investigate future proofing changes to live restore

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Live Restore
    • Storage Engines
    • 5
    • StorEng - Defined Pipeline

      Motivating PR comment here.

      This ticket is to think about future proofing live restore in case we make breaking changes in future, such as adding or removing new states. An important case to consider is if we could start live restore using "version 1" but then continue the restore at a later date with code implementing "version 2".

      We've seen cases like this before, for example the logging system is now up to version WT_LOG_V5_VERSION so we can use that as a point of reference.

            Assignee:
            backlog-server-storage-engines [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            andrew.morton@mongodb.com Andrew Morton
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: