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

XMLWordPrintableJSON

    • Fully Compatible
    • Repl 2019-02-11
    • 50
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Jason Chan
            Reporter:
            Pavithra Vetriselvan
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: