Fix the live configuration options to not be prepended by wiredTiger

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Minor - P4
    • 8.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Engines
    • Fully Compatible
    • StorEng - 2025-03-14
    • 2
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      The wiredtiger live restore configuration options are a bit repetitive. An example configuration file using them could look like:

       replication:
         replSetName: rs1
      storage:
         dbPath: new_db/
         wiredTiger:
        	engineConfig:
                 wiredTigerLiveRestoreSource: /home/ec2-user/mount_point/data/rs1
                 wiredTigerLiveRestoreThreads: 5
                 wiredTigerLiveRestoreReadSizeMB: 1
                 cacheSizeGB: 5

      We should remove the wiredTiger from the start of the configuration names so they are consistent with other WiredTiger settings.

      Additionally the test should utilize the WT_LIVE_RESTORE_COMPLETE state in the WiredTiger.h file instead of hardcoding the number 2.

            Assignee:
            Sean Watt
            Reporter:
            Sean Watt
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: