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

Implement assert=durable_timestamp

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • WT3.2.0, 4.1.9
    • Affects Version/s: None
    • Component/s: None
    • None
    • 5
    • Storage Engines 2019-01-14, Storage Engines 2019-01-28, Storage Engines 2019-02-11, Storage Engines 2019-02-25

      When “assert=durable_timestamp” is configured for a table, committing a prepared transaction will check for each update U’ in the transaction with previous version U that  U’.commit_timestamp > U.durable_timestamp. This assertion to be used for checkpoint durable tables. This assertion will ensure that the versions of updates will become durable in the same order as oldest to newest version. If durable timestamp is managed in monotonically increasing order across the system, this assertion can be disabled to improve the performance.

            Assignee:
            luke.pearson@mongodb.com Luke Pearson
            Reporter:
            vamsi.krishna@mongodb.com Vamsi Boyapati
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: