[SERVER-40821] Do not run convert_to_capped_collection*.js FSM workloads in the concurrency_simultaneous*.yml tests suites Created: 25/Apr/19  Updated: 29/Oct/23  Resolved: 26/Apr/19

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 4.1.11

Type: Improvement Priority: Major - P3
Reporter: Gregory Wlodarek Assignee: Gregory Wlodarek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Sprint: Storage NYC 2019-05-06
Participants:
Linked BF Score: 18

 Description   

The convertToCapped command consistently takes minutes to acquire a global lock in FSM testing, and when it does, background operations on the database causes it to fail. This causes the assert.soon() to timeout on multiple occasions due to how long convertToCapped takes to run in certain scenarios. Removing convertToCapped from FSM testing would resolve these issues.



 Comments   
Comment by Githook User [ 26/Apr/19 ]

Author:

{'name': 'Gregory Wlodarek', 'username': 'GWlodarek', 'email': 'gregory.wlodarek@mongodb.com'}

Message: SERVER-40821 Do not run convert_to_capped_collection*.js FSM workloads in the concurrency_simultaneous*.yml tests suites
Branch: master
https://github.com/mongodb/mongo/commit/3775fea56b0bc82ef838fa10701d2f3ea6d0ac9f

Comment by Gregory Wlodarek [ 26/Apr/19 ]

max.hirschhorn I think it's reasonable to only disable it in the concurrency_simultaneous*.yml test suites as that's where we've seen all the BFGs originate.

Comment by Max Hirschhorn [ 25/Apr/19 ]

Is this ticket proposing we not run the convert_to_capped_collection*.js FSM workloads in the concurrency_simultaneous*.yml test suites, or in any concurrency*.yml test suites?

Generated at Thu Feb 08 04:56:03 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.