[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:
Depends
Related
related to SERVER-55269 Complete TODO listed in SERVER-55192 Closed
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 SERVER-54985 which is currently under review. Until it is merged, we can simply disable the test and later re-enable it.



 Comments   
Comment by Githook User [ 15/Mar/21 ]

Author:

{'name': 'Dan Larkin-York', 'email': 'dan.larkin-york@mongodb.com', 'username': 'dhly-etc'}

Message: SERVER-55192 Disable problematic timeseries concurrency test until deadlock is fixed
Branch: master
https://github.com/mongodb/mongo/commit/c229494bfe372c2578b0a69f8ab1e0733fcffed0

Generated at Thu Feb 08 05:35:45 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.