[SERVER-39443] Apply "prepareTransaction" command on secondary Created: 08/Feb/19  Updated: 29/Oct/23  Resolved: 26/Mar/19

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

Type: Task Priority: Major - P3
Reporter: Siyuan Zhou Assignee: Matthew Russotto
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-39441 Write the new prepare command on primary Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2019-03-11, Repl 2019-03-25, Repl 2019-04-08
Participants:

 Comments   
Comment by Suganthi Mani [ 28/Mar/19 ]

matthew.russotto, currently, while replaying the ops in prepared txn as part of commit oplog replay during the recovery/initial sync, the writes are committed w/o any commit & durable timestamp. It can lead to problem data visibility and durability. So, we should prepare and commit the transaction like in SERVER-39782.

Comment by Githook User [ 26/Mar/19 ]

Author:

{'name': 'Matthew Russotto', 'username': 'mtrussotto', 'email': 'matthew.russotto@10gen.com'}

Message: SERVER-39443 Apply prepared transactions on secondary with the new > 16MB transaction oplog format.
Branch: master
https://github.com/mongodb/mongo/commit/d9d6f2d08a8539b4288185165729d5ded205f142

Comment by Siyuan Zhou [ 06/Mar/19 ]

SERVER-38588 will let background index build stall prepared transactions on secondaries. We need the same logic for large transactions.

Comment by Siyuan Zhou [ 21/Feb/19 ]

We will have a different ticket to track the update on transaction table on secondaries, so this ticket doesn't have to include the derived operation.

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