WiredTiger support for dumping and analyzing data from disagg databases

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: PALI, Tools
    • None
    • Storage Engines, Storage Engines - Foundations
    • None
    • None

      WT engineers rely on several tools to analyze the state and content of databases – mostly during testing and debugging, but occasionally when helping to understand or remediate customer issues.

      The primary tools are the wt utility and the wt_binary_decode.py script.

      Today both of these tools work by reading WT files (or portions of WT files) from the local file system.

      With disaggregated storage, WT data will no longer be stored on a local file system and will not be accessible via the file system API.

      The goal of this ticket is to:

      • Enumerate the functionality we need for disaggregated storage clusters from such tools
      • Decide on a plan for implementating that functionality
      • Implementing and validating the resulting solution

      This might turn into a small(?) project rather than a single ticket.

            Assignee:
            [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            Keith Smith
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: