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

Stop pinning stable timestamp behind prepared transactions

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.1.10
    • Component/s: Replication
    • Labels:

      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

              • Votes:
                0 Vote for this issue
                Watchers:
                10 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: