[SERVER-35226] now that createCollection and createDatabase in sharding take an in-memory lock, increase threadCount and iterations in fsm workloads Created: 25/May/18  Updated: 29/Oct/23  Resolved: 19/May/23

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 4.0.0-rc0
Fix Version/s: 4.1 Desired, 7.1.0-rc0

Type: Improvement Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: Pol Pinol
Resolution: Fixed Votes: 0
Labels: LamontN, remove-distributed-lock-fallout, sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-31567 reduce number of threads and iteratio... Closed
related to SERVER-33639 Concurrent writes against non-existen... Closed
related to SERVER-33516 make _configsvrCreateCommand take the... Closed
Assigned Teams:
Sharding EMEA
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2023-05-29
Participants:

 Description   

This will stress-test the NamespaceSerializer, because these were the tests that were failing due to too much contention on the distlock before.

 



 Comments   
Comment by Githook User [ 19/May/23 ]

Author:

{'name': 'Pol Pinol Castuera', 'email': 'pol.pinol@mongodb.com', 'username': 'PolPinol'}

Message: SERVER-35226 Increase threadCount and iterations in fsm workloads performing createCollection concurrently from many threads
Branch: master
https://github.com/mongodb/mongo/commit/eca0ce81e0415f5fa9bbf33d821867b49c53c739

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