[SERVER-55192] Disable problematic timeseries concurrency test until deadlock is fixed Created: 15/Mar/21 Updated: 29/Oct/23 Resolved: 15/Mar/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Dan Larkin-York | Assignee: | Dan Larkin-York |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Sprint: | Execution Team 2021-03-22 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 146 | ||||||||||||
| Description |
|
Currently there is one place where there is a lock order inversion in the BucketCatalog, where a caller tries to take a lock on the stats mutex while holding a lock on a bucket mutex. This leads to deadlock (and subsequently test timeouts) in jstests/concurrency/fsm_workloads/create_timeseries_collection.js. The underlying behavior should be fixed by |
| Comments |
| Comment by Githook User [ 15/Mar/21 ] |
|
Author: {'name': 'Dan Larkin-York', 'email': 'dan.larkin-york@mongodb.com', 'username': 'dhly-etc'}Message: |