Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-39689

Test that transactions prepared before the stable timestamp are prepared after rollback

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.1.11
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Sprint:
      Repl 2019-03-11, Repl 2019-03-25, Repl 2019-04-08, Repl 2019-04-22

      Description

      Currently, since we pin the stable timestamp behind the prepare timestamp, we do not have rollback test coverage for transactions that were prepared before the stable timestamp. 

      We would only allow it to move forward after its commit/abort oplog entry has been majority committed, which means that it would not be in the prepared state during a rollback.

      Once we stop pinning the stable timestamp, we should test that transactions prepared before the stable timestamp end up in the prepared state after a rollback.

        Attachments

          Activity

            People

            Assignee:
            pavithra.vetriselvan Pavithra Vetriselvan
            Reporter:
            pavithra.vetriselvan Pavithra Vetriselvan
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: