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

Stop pinning stable timestamp behind prepared transactions

    XMLWordPrintableJSON

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.1.10
    • Replication
    • None
    • Fully Compatible
    • Repl 2019-02-25, Repl 2019-03-11, Repl 2019-03-25, Repl 2019-04-08
    • 10

    Description

      We will no longer pin the stable timestamp behind the oldest prepare timestamp, or behind the oldest prepare timestamp of a transaction whose corresponding commit/abort oplog entries have not been majority committed. That is, we will revert SERVER-35811.

      Attachments

        Issue Links

          Activity

            People

              pavithra.vetriselvan@mongodb.com Pavithra Vetriselvan
              tess.avitabile@mongodb.com Tess Avitabile (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: