[SERVER-47062] Trigger hang analyzer for writeConcern timeout errors Created: 23/Mar/20 Updated: 29/Oct/23 Resolved: 17/Apr/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: | Lingzhi Deng | Assignee: | Lingzhi Deng |
| 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-04-06, Repl 2020-04-20 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 0 | ||||||||||||
| Description |
|
Similar to
|
| Comments |
| Comment by Githook User [ 17/Apr/20 ] |
|
Author: {'name': 'Lingzhi Deng', 'email': 'lingzhi.deng@mongodb.com', 'username': 'ldennis'}Message: |
| Comment by Brooke Miller [ 24/Mar/20 ] |
|
Based on the discussion with the STM Team, this requires adding mongorunner.runHangAnalyzer() to writeConcernErrors. Please ensure that expected failures do not trigger the hang analyzer. You can disable the hang analyzer on a case by case basis using mongorunner.runHangAnalyzer.disable(). |