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

Use the durable timestamp to determine if a page should stay dirty

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor - P4
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: WT3.2.0, 4.1.11
    • Component/s: None
    • Labels:
      None
    • Story Points:
      5
    • Sprint:
      Storage Engines 2019-04-22

      Description

      We found a test case using rollback_to_stable that didn't exclude data with a durable timestamp greater than the stable timestamp as it should.
      A new test case added as part of SERVER-40422 is failing. The data with the durable timestamp greater than the current stable timestamp is not discarded when rollback to stable is performed.

      testcase is : commit_transaction_rollback_recovery_data_already_applied.js

        Attachments

          Issue Links

          is depended on by

          Task - A task that needs to be done. SERVER-40422 Add a test to test replaying prepare oplog entry behind stable timestamp as part of replaying commit oplog entry during rollback recovery and with a very small wiredTiger cache size.

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

            Activity

              People

              Assignee:
              vamsi.krishna Vamsi Boyapati
              Reporter:
              vamsi.krishna Vamsi Boyapati
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: