Stop pinning stable timestamp behind prepared transactions

XMLWordPrintableJSON

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

      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
            Reporter:
            Tess Avitabile (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: