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

Support read only database connections with live restore

    • Type: Icon: New Feature New Feature
    • Resolution: Unresolved
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: Live Restore
    • Storage Engines
    • 8

      Readonly mode breaks some assumptions that live restore makes about regular files. Live restore will attempt to atomically copy those files on open, if they don't exist.

      This is a write operation to the destination and not legal in readonly mode. Working around this is relatively trivial but it changes a lot of the assumed semantics around the live restore file handle.

      Thus the changes to support read only mode will likely propagate a bit throughout the live_restore_fs.c file. Additionally the server must avoid creating background threads in readonly mode but that is a trivial change.

      Scope:

      • Support live restore running in readonly mode

            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: