-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Cluster Scalability
-
Fully Compatible
-
ALL
-
v8.0
-
200
In suites that enable random migrations and pauseMigrationsDuringMultiUpdates, the number of moveCollections can starve multi writes made by the test, causing the test to take a very long time to complete (see this comment for a specific example).
In suites where both of these options are configured, consider either also setting skipMoveCollectionThreshold as is done here, or maybe adding a sleep to the balancer to throttle the number of moveCollections being run.
- is related to
-
SERVER-91655 Re-enable timeseries_predicates js test for sharding_jscore_passthrough_with_balancer suites
- Backlog
-
SERVER-91722 Re-enable geo_update_btree for sharding_jscore_passthrough_with_balancer suites
- Backlog