[SERVER-35816] Ensure the commit optime is less than or equal to the optime of the commitTransaction oplog entry Created: 26/Jun/18  Updated: 29/Oct/23  Resolved: 21/Sep/18

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.1.4

Type: Task Priority: Major - P3
Reporter: Gregory McKeon (Inactive) Assignee: Judah Schvimer
Resolution: Fixed Votes: 0
Labels: prepare_errors
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-35865 Write commit oplog entry on commit of... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2018-07-30, Repl 2018-08-13, Repl 2018-08-27, Repl 2018-09-10, Repl 2018-09-24
Participants:

 Comments   
Comment by Githook User [ 21/Sep/18 ]

Author:

{'name': 'Judah Schvimer', 'email': 'judah@mongodb.com', 'username': 'judahschvimer'}

Message: SERVER-35865 SERVER-35816 SERVER-35730 Write commit oplog entry on commit of prepared transaction
Branch: master
https://github.com/mongodb/mongo/commit/340e33483d69983c976dff0ed5ab2ff0b036237c

Comment by Judah Schvimer [ 14/Sep/18 ]

This ticket will be committed in the same patch as SERVER-35865.

Comment by Judah Schvimer [ 12/Jul/18 ]

This ticket should also make sure that the commit optime is greater than or equal to the prepare optime

Comment by Judah Schvimer [ 26/Jun/18 ]

Yes, in this case all shards will need the commit oplog entry timestamp to be greater than 20. It would be very strange to have writes at a timestamp greater than the top of the oplog.

Comment by Esha Maharishi (Inactive) [ 26/Jun/18 ]

CC judah.schvimer

Comment by Esha Maharishi (Inactive) [ 26/Jun/18 ]

Will this require bumping the logical time on all participants to be equal to or greater than the commitTransaction oplog entry?

I'm imagining:

shardA: prepareTimestamp = 5

shardB: prepareTimestamp = 10

shardC: prepareTimestamp = 20

--> commitTimestamp = 20

But on shardA and shardB, the commitTimestamp might be > the commitTransaction oplog entry timestamp?

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