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

Give applications a chance to handle panic before API panic returns

    XMLWordPrintable

Details

    • New Feature
    • Status: Closed
    • Minor - P4
    • Resolution: Fixed
    • None
    • 4.1.7, WT3.2.0, 4.0.7
    • None
    • None
    • Storage Engines 2019-01-14
    • v4.0

    Description

      When a panic happens, WiredTiger sets the connection level panic flag and then calls the underlying application error function with the WT_PANIC flag.

      As soon as the connection level panic flag is set, application threads will return WT_PANIC from WiredTiger API calls, those threads might race with the thread of control setting the panic flag, and the application might save stack information from an uninteresting API thread, simply because it's the first WT_PANIC the application saw.

      Change WiredTiger to wait for the underlying application error function to return before setting the connection-level panic flag, ensuring the application has the opportunity to save the interesting thread stack information.

      Attachments

        Issue Links

          Activity

            People

              keith.bostic@mongodb.com Keith Bostic (Inactive)
              keith.bostic@mongodb.com Keith Bostic (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: