Add logging information for debugging ref->page == NULL

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • WT12.0.0, 9.1.0-rc0
    • Affects Version/s: None
    • Component/s: Logging
    • None
    • Storage Engines - Transactions
    • 232.071
    • SE Transactions - 2026-07-17
    • 5
    • v9.0

      BF-44437 encounters an issue where ref->page == NULL and we are trying to read or reconstruct a modify when the full base value is unavailable. This suggests that  __wt_modify_reconstruct_from_upd_list() failing to find a full update in the update chain and falling back to the on-page value via the upd == NULL path, but with the original page is missing.

      The crash came from a resmoke run of jstests/core/query/query_settings/query_settings_size_limits.js on a disaggregated replset.

      To debug the issue, we can add extra diagnostic information in that spot that would call __wt_value_return_buf with the missing page, and check if cbt->ref == NULL || cbt->ref->page == NULL and, if so: log the full state and abort here, instead of downstream __wt_value_return_buf deref.

            Assignee:
            Alana Huang
            Reporter:
            Alana Huang
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: