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

Add option to not abort in diagnostic builds on data corruption

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • WT10.0.0, 4.4.2, 4.9.0
    • None
    • 5
    • Storage - Ra 2020-09-21, Storage - Ra 2020-10-05, Storage - Ra 2020-10-19, Storage - Ra 2020-11-02

    Description

      Any time WiredTiger returns a WT_PANIC error and diagnostic mode is enabled we currently abort the process - we do that to aid in debugging unexpected failures.

      There are a category of issues that lead to WT_PANIC error returns which are due to an underlying data corruption - in those cases it's not helpful to abort and generate a core file, because the corruption is generally due to either an on disk failure or fallout from something that happened a long time in the past.

      The reason this matters is for test cases attempting to cover data corruption cases need to behave differently when diagnostic mode is enabled if WT_PANIC triggers and abort.

      Attachments

        Issue Links

          Activity

            People

              sulabh.mahajan@mongodb.com Sulabh Mahajan
              alexander.gorrod@mongodb.com Alexander Gorrod
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: