[SERVER-76846] Missing gdb/hang-analyser utilities for debugging the admission control subsystem Created: 04/May/23  Updated: 09/May/23

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

Type: Improvement Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Backlog - Storage Execution Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Storage Execution
Participants:
Linked BF Score: 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.

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