[SERVER-39437] Allow secondaries to see “abort” oplog entry on non-existent transactions Created: 08/Feb/19  Updated: 29/Oct/23  Resolved: 14/Feb/19

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

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

Backwards Compatibility: Fully Compatible
Sprint: Repl 2019-02-25
Participants:

 Description   

For large transacations, if a transaction has written any oplog entry, “abort” must write a corresponding oplog entry. We don't need to write an abort oplog entry if the transaction hasn't written anything, but we may do it sometimes out of convenience and this must be safe. Thus secondaries should be ready to see abort oplog entries for non-existent transactions.



 Comments   
Comment by Githook User [ 14/Feb/19 ]

Author:

{'name': 'Jason Chan', 'email': 'jason.chan@10gen.com'}

Message: SERVER-39437 Add test to ensure secondaries can abort non-existent transactions.
Branch: master
https://github.com/mongodb/mongo/commit/6f4155b0fb8b4e93ea09afdd397f5b391d7fd99a

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