[SERVER-28747] Enhance locks output with lock names Created: 11/Apr/17 Updated: 06/Dec/22 Resolved: 11/May/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Eddie Louie | Assignee: | Backlog - Server Tooling and Methods (STM) (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | stm, tig-hanganalyzer | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Server Tooling & Methods
|
||||||||
| Participants: | |||||||||
| Description |
|
Currently the output from mongodb-show-locks and mongodb-waitsfor-graph only outputs the locks by their addresses. This makes it difficult to reconcile which locks are actually being held. Ideally we could add lock names and the file and line number where it was acquired or being waited for. This will help in cases where a lock was acquired deep in a call stack before the thread ultimately blocks. |
| Comments |
| Comment by Ryan Timmons [ 11/May/20 ] |
|
Closing as wont-fix to indicate that there is currently no intention of doing this. Please re-open if there is priority for this. Perhaps this change could self-service by an appropriate server team if this is necessary rather than having to go thru the STM prioritization queue. |