ExportXMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • WT12.0.0, 9.1.0-rc0
    • Affects Version/s: None
    • Component/s: Truncate
    • None
    • Storage Engines - Foundations
    • 528.818
    • SE Foundations - 2026-10-27, SE Foundations - 2026-11-10
    • 5

      Description

      Under disagg.mode=switch with fast truncate enabled, reconcile on stable trips the __timestamp_no_ts_fix assertion select_tw->stop_txn >= select_tw->start_txn. Reproduces at ~5% of CONFIG.fail runs.

      Root cause

      WT-17272 (1) was not implemented. The truncate-vs-uncommitted-single-key-update case remains: there is no chain visibility check on the truncate-ingest path.

      Short term fix

      Since write conflict detection is properly implemented and we need testing for switch mode, we will serialise all truncates. All truncates can't have a contending write in test/format.

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

              Created:
              Updated:
              Resolved: