[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: |
|
||||||||
| 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: |