Enable disagg testing (-G) for schema abort tests as part of crash recovery scenario testing

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Schema Management
    • Security Level: Public (Available to anyone on the web)
    • Storage Engines, Storage Engines - Foundations
    • 4,063.586
    • SE Foundations - 2026-07-07
    • 5

      Background

      We have extensively tested the “happy path” for WT (in test/format & python suite) for disagg, but crash recovery scenarios require additional testing.

      Schema abort tests perform schema operations (table create, table drop) and randomly crash the system to verify whether it can recover to an expected state. This is important to ensure:

      • Consistency after unexpected crashes
      • Reliability of schema changes under failure conditions
      • Confidence in crash recovery logic.

      Following WT-16681, disagg mode can be easily enabled with the -G option for any csuite test. A similar approach was successfully used for timestamp_abort (WT-16349), where enabling disagg at the table level was sufficient.

      Problem Statement

      • Currently, schema abort tests do not run in disagg mode
      • Without this, some failure scenarios may go undetected

      Expected Outcome

      • Schema abort tests run in disagg mode

      Out of Scope

      • Fixing any WT bugs that are uncovered as a result of schema abort tests

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

              Created:
              Updated:
              Resolved: