[disagg] test/format switch/leader: __wti_delete_page_instantiate 'page->entries > 0' assertion abort reading WiredTigerSharedHS.wt_stable

XMLWordPrintableJSON

    • Type: Build Failure
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None

      Signature

      WiredTiger library aborts on assertion page->entries > 0 in __wti_delete_page_instantiate (src/btree/bt_delete.c:690) while instantiating a fast-truncated deleted page during a search_near on the shared history store file:WiredTigerSharedHS.wt_stable.

      __wt_abort  (os_abort.c:32)
__wti_delete_page_instantiate  (bt_delete.c:690: 'page->entries > 0')
__page_read  (bt_read.c:485)
__wt_page_in_func  (bt_read.c:610)   func=__wt_row_search
__wt_row_search  (row_srch.c:576)
__cursor_row_search / __cursor_search  (bt_cursor.c)
__wt_btcur_search_near  (bt_cursor.c:975)
__curfile_search_near  (cur_file.c:366)
__curhs_file_cursor_search_near  (cur_hs.c:226)
__curhs_search_near / __curhs_search_near_helper  (cur_hs.c)

      Scope

      First seen on wiredtiger @ 397a2328. Reproduces across disagg switch and leader format-stress variants (arm64 / asan / non-standalone). Grouped from 7 BFG instances.

      Triage notes

      BuildBaron's top suggestions (WT-17822 disagg-switch mirror mismatch, WT-16826 __wt_col_search 'base > 0', WT-18125 Closed/Fixed) do not match this assertion — different function and different failure. The underlying task-log faults were masked by WT-18090 installer.sh toolchain noise; the real signature was recovered from the extracted stack traces. Distinct from the mirror data-mismatch failure tracked separately (table_verify_mirror).

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

              Created:
              Updated: