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

Write "abort" oplog entry when aborting unprepared transaction with replicated operations

    XMLWordPrintableJSON

Details

    • Fully Compatible
    • Repl 2019-05-06, Repl 2019-05-20

    Description

      We are exposing in-progress transactions in the oplog for large transactions. Due to the requirement of Oplog Maintenance, it becomes necessary to expose the entire lifetime of transactions, including abort, to secondaries. Thus we need to always write an abort oplog entry whenever an in-progress unprepared transaction with replicated operations is aborted. Prepared transactions are already aborted with an oplog entry.

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: