-
Type: Improvement
-
Resolution: Won't Do
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Concurrency, Diagnostics
-
(copied to CRM)
Currently we report how long threads waited to acquire locks, but it is harder to find the reason why the lock wasn't granted. By adding statistics on how long a locker holds a lock while blocking other threads, we could surface problematic lockers.
This should be straightforward to implement, because we already have the appropriate lock manager bucket locked when queuing the request, so we can just add a start block time to the granted request.
- is related to
-
SERVER-53180 Log each operation that holds a lock for an extended period of time without yielding
- Closed