ExportXMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Not Applicable
    • None
    • Storage Engines - Transactions
    • 26.896
    • SE Transactions - 2026-12-18
    • None

      Description

      Extend test_layered_cursor_stress.py with randomized prepared-transaction and role-change coverage requested in PR #14786 and followed up in PR #15102.

      This is separate from the deterministic combinations tracked by WT-19103 and complements the broader stress improvements in WT-17838.

      Scope

      • Generate prepared inserts, updates and removes in both stable and ingest, including shared keys and multiple prepared keys.
      • Exercise forward/reverse iteration, direction changes, repeated conflicts, and continuation after prepared transactions commit or roll back.
      • Include supported step-up/step-down sequences and applicable mirroring configurations. Respect transaction and cursor restrictions; do not treat the debug prepare/step-down bypass as supported behavior. Prepared transactions spanning asynchronous step-down remain separate work under WT-18422.
      • Compare results with an appropriate ordinary-cursor reference or model using equivalent visibility and read timestamps.

      Acceptance criteria

      • Verify exact ordered keys and values, operation results, and end-of-scan behavior, detecting omissions, duplicates and stale values.
      • Preserve the same cursor and read transaction across prepare conflicts where supported. Do not reset or reposition cursors merely to hide differences from the reference.
      • Assert expected conflicts explicitly; document any permitted differences in conflict timing rather than silently accepting them.
      • Use selectable, reproducible seeds and log the seed/configuration before cursor operations. Include enough operation history to reproduce failures.
      • Run multiple seeds, preserve discovered failures as focused deterministic regressions, and document excluded lifecycle combinations and their tracking tickets.

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

              Created:
              Updated: