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

Stop pinning stable timestamp behind prepared transactions

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.1.10
    • Affects Version/s: None
    • Component/s: Replication
    • Labels:
      None
    • Fully Compatible
    • Repl 2019-02-25, Repl 2019-03-11, Repl 2019-03-25, Repl 2019-04-08
    • 10

      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.

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

              Created:
              Updated:
              Resolved: