[SERVER-39782] Replaying prepared transaction writes for commit oplog entry during replication recovery and initial sync should set commit and durable timestamp for those writes. Created: 22/Feb/19  Updated: 29/Oct/23  Resolved: 28/Mar/19

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

Type: Bug Priority: Major - P3
Reporter: Suganthi Mani Assignee: Suganthi Mani
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on WT-4607 Allow prepared transaction to commit ... Closed
depends on SERVER-40008 Storage Interface changes to specify ... Closed
depends on WT-4621 Support rounding up prepare timestamp... Closed
Related
related to SERVER-39035 Specify durable_timestamp when commit... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2019-03-11, Repl 2019-03-25, Repl 2019-04-08
Participants:

 Description   

Currently, when we commit a prepared transaction as a part of commit oplog replay, we don't set any timestamp (commit & durable timestamp) to the wiredTiger transaction via recovery unit. So, basically we are committing the write operations as non-timestamped. This would cause problem for data visibility and durability.



 Comments   
Comment by Githook User [ 28/Mar/19 ]

Author:

{'email': 'suganthi.mani@mongodb.com', 'name': 'Suganthi Mani', 'username': 'smani87'}

Message: SERVER-39782 Replaying prepared transaction writes for commit oplog entry during
replication recovery and initial sync should set commit and durable
timestamp for those writes.
Branch: master
https://github.com/mongodb/mongo/commit/3d67051935b04db3d0a66202a8ebfcce793858de

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