The ConcurrentCatalogWriteBatchingMayThrow test case sets up 50000 collections on the catalog. This can take some time, and on slow debug build variants may cause execution timeouts.
Given that this large number was chosen arbitrarily to try to achieve a certain interleaving (which is already a flaky setup), we should rewrite this test case in a more deterministic and less resource-intensive way.
- is caused by
-
SERVER-53665 Increase number of Collections in ConcurrentCatalogWriteBatches test to make it less flaky
-
- Closed
-
-
SERVER-53885 Make ConcurrentCatalogWriteBatches unittest more deterministic
-
- Closed
-
- related to
-
SERVER-105108 Simplify CollectionCatalog::write()
-
- Closed
-