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

Ensure that secondaries correctly pin the stableTimestamp when there are prepared transactions

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.1.8
    • Component/s: Replication

      Description

      We write the prepare oplog entry here, but this only occurs on the primary. On a secondary, the prepareOpTime would be null.

      This could be a problem on secondaries because the stableTimestamp would always move forward, causing us to possibly commit a transaction before the stableTimestamp.

        Attachments

          Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-38620 prepareTransaction call doesn't set _prepareOpTime if transaction was recovered

          • Major - P3 - Major loss of function.
          • Closed

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: