[SERVER-64178] Add RecoveryUnit debug logs to WT::begin_transaction() calls Created: 03/Mar/22  Updated: 26/Oct/23

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

Type: Improvement Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Backlog - Storage Execution Team
Resolution: Unresolved Votes: 0
Labels: former-storex-namer, neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-66603 Ensure we can't throw between releasi... Closed
Assigned Teams:
Storage Execution
Participants:
Linked BF Score: 0

 Description   

We have a test failure wherein an error occurs to the effect that a WT transaction is already open when the MDB layer calls WT::begin_transaction – it has already been called once and calling it again is not supported.

It isn't obvious where the issue is, that the MDB layer is double calling or not. The RecoveryUnit is supposed to track state for storage engine access – active, inactive, WUOW, etc. --, so it might be helpful to log some of that information before proceeding to call invariantWTOK on the WT::begin_transaction() calls. Assuming the RecoveryUnit doesn't have a bug, that is. Hopefully RU state will be enlightening regardless.


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