[SERVER-48018] Improve the lock manager to dump locks being held by clients stashed in the AlternativeClientRegion Created: 07/May/20 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Gregory Wlodarek | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Unresolved | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Storage Execution
|
||||
| Participants: | |||||
| Linked BF Score: | 22 | ||||
| Description |
|
We have quite a few spots where we use the AlternativeClientRegion in the code. Currently, when we dump the lock manager, none of the stashed client's locks are being collected and shown, which would be useful to have in the event that we deadlock with a stashed client. |