[SERVER-39828] Track the first timestamp of transaction in transaction table Created: 25/Feb/19  Updated: 06/Dec/22  Resolved: 06/Mar/19

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

Type: Task Priority: Major - P3
Reporter: Siyuan Zhou Assignee: Backlog - Replication Team
Resolution: Duplicate Votes: 0
Labels: bigtxns_recovery
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-39680 Maintain the oldest active transactio... Closed
Related
related to SERVER-39829 Consider in-progress transactions whe... Closed
Assigned Teams:
Replication
Participants:

 Description   

With SERVER-39680, we'll compute the oldest active transaction timestamp by reading the transaction table. For prepared transactions, prevOpTime happens to be the first optime of the transaction in the old applyOps format. With the new format of both unprepared and prepared transactions, we need to add a new field in the transaction table to track the first timestamp of any oplog entry in a transaction.



 Comments   
Comment by Siyuan Zhou [ 06/Mar/19 ]

As part of SERVER-39680, Jesse added the startTimestamp field in 74eb8f3c5.

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