[SERVER-38672] Remove FCV check for writing an abort oplog entry Created: 17/Dec/18  Updated: 27/Oct/23  Resolved: 26/Aug/19

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

Type: Task Priority: Major - P3
Reporter: Tess Avitabile (Inactive) Assignee: Backlog - Replication Team
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Replication
Participants:

 Description   

The TransactionParticipant only writes an abort oplog entry for unprepared transactions if the FCV is 4.2, since 4.0 nodes do not recognize abort oplog entries. This check can be removed once 4.2 is the last-stable version.



 Comments   
Comment by Jason Chan [ 26/Aug/19 ]

This work is no longer needed as we decided against writing an explicit abort oplog entry for unprepared transactions all the time in v4.2

We only write an abort oplog entry for aborting prepared transactions and if a new primary steps up with an in-progress transaction for any reason. The latter might happen if the old primary fails before the entire transaction has fully replicated to the secondary (now the new primary). This case won't exist in FCV 4.0 because multi-oplog transactions are gated for FCV4.2 and above.

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