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

Allow secondaries to see “abort” oplog entry on non-existent transactions

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.1.9
    • None
    • Replication
    • None
    • Fully Compatible
    • Repl 2019-02-25

    Description

      For large transacations, if a transaction has written any oplog entry, “abort” must write a corresponding oplog entry. We don't need to write an abort oplog entry if the transaction hasn't written anything, but we may do it sometimes out of convenience and this must be safe. Thus secondaries should be ready to see abort oplog entries for non-existent transactions.

      Attachments

        Activity

          People

            jason.chan@mongodb.com Jason Chan
            siyuan.zhou@mongodb.com Siyuan Zhou
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: