Details
-
Improvement
-
Resolution: Unresolved
-
Major - P3
-
None
-
None
-
None
-
None
-
Storage Execution
-
107
Description
The admission control subsystem was placed deep in the lock manager code path so it depends a lot on the kind of locking that an operation does and on properties of the operation context. Because of this it is very difficult when looking at a core dump from a timed out test to know what thread owns what and we lack the gdb scripts and the hang-analyser integration to help navigate it. This became evident during the investigation of SERVER-76834.
This ticket is a request to add utilities to gdb which at least can show the following:
- Dump all threads that are holding or waiting on a ticket and what kind
- Dump all threads that are waiting on a ticket while they hold a lock/mutex/etc.