Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-4502

Assertion checking hazard pointers on page discard is too strong

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: WT3.2.1, 4.3.1, 4.2.0-rc3, 4.0.13
    • Component/s: None
    • Labels:
      None
    • Story Points:
      8
    • Sprint:
      Storage Engines 2019-07-01
    • Backport Requested:
      v4.0

      Description

      This is a follow-on ticket to WT-4280, which enhanced debugging to dump session info the hazard pointers. Use this ticket to address the root cause. 

       

      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 

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              keith.bostic Keith Bostic
              Reporter:
              luke.chen Luke Chen
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: