[SERVER-71054] TransactionParticipant last write optime should be null at the beginning of logOplogEntries Created: 03/Nov/22  Updated: 29/Oct/23  Resolved: 04/Nov/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.2.0-rc0

Type: Improvement Priority: Major - P3
Reporter: Benety Goh Assignee: Benety Goh
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-70899 move logOplogEntries() from OpObserve... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2022-11-14
Participants:

 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.



 Comments   
Comment by Githook User [ 04/Nov/22 ]

Author:

{'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}

Message: SERVER-71054 TransactionParticipant should have a null last write optime before writing applyOps entries
Branch: master
https://github.com/mongodb/mongo/commit/4edd845c1633fb81371eed99b3d73075a3b929b5

Generated at Thu Feb 08 06:17:55 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.