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

Update debugging when committing at an earlier timestamp

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.6.3, 3.7.2, WT3.1.0
    • None
    • None
    • Storage 2018-01-29

    Description

      In WT-3597 code was added that caused an error if a data item was updated at a later time but at an earlier timestamp. That started causing several secondary tests to fail because some of that code is not yet ready. That change was modified to be a verbose message instead of a failure. This ticket is for less aggressive ways to still trigger and detect the error without causing widespread failures.

      Attachments

        Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. WT-3881 key timestamp consistency checking should not check its own updates

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. WT-3597 Add a diagnostic check for updates to the same key out of timestamp order

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              sue.loverso@mongodb.com Susan LoVerso
              sue.loverso@mongodb.com Susan LoVerso
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: