[SERVER-72574] Ability to dump lock manager upon lock request timeout Created: 05/Jan/23 Updated: 29/Oct/23 Resolved: 11/Jan/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0, 6.0.6 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Gregory Noma | Assignee: | Gregory Noma |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Backport Requested: |
v6.0
|
||||||||
| Sprint: | Execution Team 2023-01-23 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 121 | ||||||||
| Description |
|
There are certain cases where we dump the lock manager upon a lock acquisition timing out, for instance the RSTL acquisition for step down. However, since the acquisition has already timed out by this point, the state of the lock manager may have changed. It would be nice to be able to tell the locker to perform the lock manager dump before actually performing the timeout in cases this like. We could even make this a bit more general by providing a callback, so that the fatal assertion could be done at this point at well. Then we would have a more useful core dump. |
| Comments |
| Comment by Githook User [ 17/Mar/23 ] |
|
Author: {'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}Message: (cherry picked from commit 0f5cd2f543ef55a9ee6ca3e4308121c6825cd3d4) |
| Comment by Githook User [ 10/Jan/23 ] |
|
Author: {'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}Message: |