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

TransactionParticipant last write optime should be null at the beginning of logOplogEntries

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 6.2.0-rc0
    • None
    • None
    • None
    • Fully Compatible
    • Execution Team 2022-11-14

    Description

      The logOplogEntries() function, used to format applyOps oplog entries for multi-doc transactions and batched write, fetches the lastWriteOpTime from the TransactionParticipant before writing out any oplog entries. This call is redundant because the lastWriteOptime is always null and gets set in between oplog entries in a chain of applyOps entries for a large transaction.

      It should be safe to convert this TransactionParticipant::getLastWriteOpTime() to an invariant.

      Attachments

        Activity

          People

            benety.goh@mongodb.com Benety Goh
            benety.goh@mongodb.com Benety Goh
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: