[SERVER-39829] Consider in-progress transactions when calculating the oldest active transaction timestamp Created: 25/Feb/19  Updated: 29/Oct/23  Resolved: 09/Apr/19

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

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

Issue Links:
Related
is related to SERVER-39680 Maintain the oldest active transactio... Closed
is related to SERVER-39828 Track the first timestamp of transact... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2019-04-08, Repl 2019-04-22
Participants:

 Description   

SERVER-39680 reads the transaction table to calculate the oldest active transaction timestamp. After tracking first timestamp of both prepared and unprepared transactions in SERVER-39828, we should take the in-progress transactions in consideration too.



 Comments   
Comment by Luke Chen [ 11/Apr/19 ]

Fixing up the fixVersion as this ticket was not included as part of 4.1.10 release.

Comment by Githook User [ 09/Apr/19 ]

Author:

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

Message: SERVER-39829 Consider in-progress transactions when calculating the oldest active transaction timestamp
Branch: master
https://github.com/mongodb/mongo/commit/6a7f5a0b9c5798b20c91f2272abd9851ea9d2909

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