[SERVER-49905] Update config.transactions entry for transaction's final oplog entry during resharding's oplog application Created: 25/Jul/20  Updated: 29/Oct/23  Resolved: 14/Jan/21

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

Type: Task Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Randolph Tan
Resolution: Fixed Votes: 0
Labels: PM-234-M2.5, PM-234-T-oplog-apply
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-49907 Implement applyOps write rule for res... Closed
Duplicate
is duplicated by SERVER-51766 Handle transactions in resharding opl... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2021-01-11, Sharding 2021-01-25
Participants:
Story Points: 1

 Description   

The transaction's final oplog entry refers to one of

  • a non-partialTxn:true, non-prepare:true applyOps entry = the final applyOps entry from a non-prepared transaction,
  • a commitTransaction oplog entry, or
  • an abortTransaction oplog entry.

Follow the procedure for updating the entries (or inserting new entries) in the config.transaction table described in the design document.



 Comments   
Comment by Githook User [ 14/Jan/21 ]

Author:

{'name': 'Randolph Tan', 'email': 'randolph@10gen.com', 'username': 'renctan'}

Message: SERVER-49905 Update config.transactions entry for transaction's final oplog entry during resharding's oplog application
Branch: master
https://github.com/mongodb/mongo/commit/e36fe5b84c5b07dbc0676bf8175f1ae7dc3cd662

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