Disagg: collection and its index can mismatch under concurrent workloads

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Critical - P2
    • None
    • Affects Version/s: None
    • Component/s: Schema Management
    • Storage Engines - Foundations
    • 61.392
    • SE Foundations - 2026-08-18
    • None

      Problem

      In disaggregated storage, a collection and its index can become inconsistent with each other: the two tables do not reflect the same state, so index entries and collection records disagree.

      Observed in the disagg_concurrency_replication suite as:

      • validate failure: "number of _id index entries (0) does not match the number of documents in the index (1000)" (agg_sort)
      • DataCorruptionDetected: "Erroneous index key found with reference to non-existent record id" (create_index_background_unique)

        1. README_wt18274_repro.txt
          1 kB
          Jie Chen
        2. test_layered_schema26.py
          4 kB
          Jie Chen
        3. wt18274_timing_hook.patch
          1 kB
          Jie Chen
        4. wt-18274-fix-and-repro.patch
          8 kB
          Salman Javed

            Assignee:
            Salman Javed
            Reporter:
            Jie Chen
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: