[SERVER-35863] Write an abortTransaction oplog entry if a transaction that may have written a prepare oplog entry aborts Created: 28/Jun/18  Updated: 29/Oct/23  Resolved: 07/Sep/18

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

Type: Improvement Priority: Major - P3
Reporter: Judah Schvimer Assignee: Judah Schvimer
Resolution: Fixed Votes: 0
Labels: prepare_durability
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-32324 Update transaction table when an abor... Closed
is depended on by SERVER-35875 Secondaries abort transactions when a... Closed
Duplicate
is duplicated by SERVER-35669 Write an abortTransaction oplog entry... Closed
Related
related to SERVER-35430 Abort a transaction if prepare fails Closed
is related to SERVER-76741 Split-prepare transactions are aborte... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2018-08-27, Repl 2018-09-10
Participants:

 Description   

It is important that this oplog entry either always happens after the prepareTransaction oplog entry, or that them being out of order is safe. It is fine if there is an abort oplog entry with no corresponding prepare oplog entry.



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

Author:

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

Message: SERVER-35863 log abortTransaction oplog entry when prepared transactions
abort
Branch: master
https://github.com/mongodb/mongo/commit/688d4fb9a0d2ab17d37c3f5ca52d4af0a3b04764

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