[SERVER-66603] Ensure we can't throw between releasing WiredTigerBeginTransactionBlock and marking recovery unit active Created: 19/May/22  Updated: 29/Oct/23  Resolved: 23/May/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.1.0-rc0

Type: Bug Priority: Major - P3
Reporter: Dan Larkin-York Assignee: Dan Larkin-York
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-64178 Add RecoveryUnit debug logs to WT::be... Open
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2022-05-30
Participants:
Linked BF Score: 0

 Description   

Currently there is a small window on a few code paths where we could conceivably throw after releasing our RAII class WiredTigerBeginTransactionBlock but before marking the RecoveryUnit active. This could result in leaving a transaction open on the underlying WT_SESSION.



 Comments   
Comment by Githook User [ 23/May/22 ]

Author:

{'name': 'Dan Larkin-York', 'email': 'dan.larkin-york@mongodb.com', 'username': 'dhly-etc'}

Message: SERVER-66603 Ensure we can't throw between releasing WiredTigerBeginTransactionBlock and marking recovery unit active
Branch: master
https://github.com/mongodb/mongo/commit/8fb1d301068e0c7132d0adfc0953129ad74ec5ed

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