Implement a mechanism in wt_verify to fix WiredTiger's metadata if it finds issues

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Checkpoints, Verify
    • None

      As part of the checkpoint size project we write values to the metadata file that indicate the size of the stable btree's, essentially the checkpoint metadata size field tracks the stable b-tree size.

      Now given we have known bugs it is likely that for all running database this size will gradually be too large. We'd like a mechanism to resolve these issues without having to re-write the whole tree, as such I am proposing a wt_verify fix=true or similar API be added.

      Then at the end of db->validate() or {{wt->verify()} the b-tree size will be updated with the correct values and we can assume that we've error corrected the production instances.

      Scope:

      • Define an API for verify that is extensible, this isn't likely to be the only use case for it
      • Implement the changes
      • Test

            Assignee:
            [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            Luke Pearson
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: