[SERVER-47764] Trigger hang analyzer for LockTimeout errors Created: 24/Apr/20 Updated: 29/Oct/23 Resolved: 12/Jun/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Samyukta Lanka | Assignee: | Samyukta Lanka |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Repl 2020-05-18, Repl 2020-06-01, Execution Team 2020-06-15, Execution Team 2020-06-29 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
It would be helpful to always have hang analyzer outputs and core dumps for LockTimeout errors, especially when it fails due to an assert.comandWorked. |
| Comments |
| Comment by Githook User [ 12/Jun/20 ] |
|
Author: {'name': 'Samy Lanka', 'email': 'samy.lanka@mongodb.com', 'username': 'lankas'}Message: |
| Comment by Samyukta Lanka [ 24/Apr/20 ] |
|
This would have been helpful for BF-16902 because this assert failed due to a LockTimeout, so we didn't have access to hang analyzer output. Without the hang analyzer output, it's very difficult to diagnose the failure. |