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

Investigate solution to an edge case in extent list import

    • Storage Engines
    • 8
    • StorEng - 2025-02-28

      A comment in __wt_live_restore_fh_import_extents_from_string describes a bad scenario in the current live restore implementation.

          /*
           * This function can be called for file handles that already have an in memory extent list. For
           * this to happen the destination file was created for the first time and a single file size
           * hole was initialized.
           *
           * There is a tricky scenario here:
           *   - Open a file that exists in the source, a.wt.
           *   - Create a new file in the destination to begin migrating the file to.
           *   - Crash.
           *   - Open the file a.wt again, we will see an a.wt in the destination and not create the
           *   necessary file length hole. We will also get an empty extent list string indicating a.wt is
           *   complete.
           */ 

      We should investigate this and fix it.

            Assignee:
            backlog-server-storage-engines [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            luke.pearson@mongodb.com Luke Pearson
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: