Add debugging to know which session has a hazard pointer

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.1.7, 4.0.6, WT3.2.0
    • Affects Version/s: 4.1.1
    • Component/s: None
    • None
    • None

      The Jenkins split stress test had a hazard check assertion failure here:

      [1535338740:356623][2153:0x7f355ffff700], file:test2, WT_CURSOR.insert: __wt_hazard_check_assert, 422: hazard pointer reference to discarded object: ((nil): __wt_row_search, line 450)
[1535338740:357616][2153:0x7f355ffff700], file:test2, WT_CURSOR.insert: __split_parent, 875: __wt_hazard_check_assert(session, next_ref, false)
[1535338740:357955][2153:0x7f355ffff700], file:test2, WT_CURSOR.insert: __wt_abort, 30: aborting WiredTiger

            Assignee:
            Susan LoVerso (Inactive)
            Reporter:
            Neha Khatri (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: