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

Enable assertion that commit timestamp is newer than all readers

    XMLWordPrintableJSON

Details

    • 3
    • Storage - Ra 2020-08-24, Storage - Ra 2020-11-16

    Description

      In WT-4738 we added a new assertion that enforced the commit timestamp for non-prepared transactions is newer than the timestamps of all active readers. That caused some test fallout, so we disabled the assertion in WT-4779.

      This ticket involves understanding the test fallout and re-enabling the assertion.

      Attachments

        Issue Links

          depends on

          Bug - A problem which impairs or prevents the functions of the product. SERVER-41333 Initial Sync and Shutdown write to the minValid document at the lastApplied

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-50398 appliedThrough document write and background validation reads could use the same timestamp

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

          Task - A task that needs to be done. SERVER-41178 TransactionHistoryIterator should do untimestamped reads during rollback recovery

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

          Bug - A problem which impairs or prevents the functions of the product. WT-4738 Tighten rules around use of timestamps

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

          Bug - A problem which impairs or prevents the functions of the product. WT-4779 Disable new assertion related to timestamp consistency

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

          Activity

            People

              haribabu.kommi@mongodb.com Haribabu Kommi
              alexander.gorrod@mongodb.com Alexander Gorrod
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: