-
Type:
New Feature
-
Resolution: Duplicate
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Storage
-
Labels:None
-
Storage Execution
There are a couple ways of going about this.
- Expose methods in WT that dumps its internal state.
- Have MDB walk Clients->OpCtx->RecoveryUnits
The latter is advantageous because it's easier to connect an OpCtx with what it was doing than a pointer to a WT session.
However, there are some gaps with walking MDB's tree. It's uncommon, but possible for recovery units to become detached as part of a "side transaction". They're temporarily stored as function locals and otherwise unable to be discovered by traversing memory structures.
If WT_CONNECTION::debug_info returned a structure, we might be able to get the best of both worlds by linking up a WT session with an OpCtx and be able to surface the dangling transactions.
- duplicates
-
SERVER-45556 Create GDB pretty printer to dump all active RecoveryUnits
-
- Closed
-
- is related to
-
SERVER-52623 Aborting in-progress transactions on step-up with eMRC=off can set the stable timestamp ahead of the all durable timestamp
-
- Blocked
-
-
-
- Closed
-
- related to
-
-
- Closed
-