-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: 8.2.0, 9.0.0-rc0, 8.3.0, 9.1.0-rc0
-
Component/s: Sharding
-
Cluster Scalability
-
ALL
-
ClusterScalability 3Aug-17Aug
-
0
-
None
-
None
-
None
-
None
-
None
-
None
-
None
The balancer_should_return_random_migrations_failpoint.js test exercises that we do random migrations if the balancerShouldReturnRandomMigrations fail point is enabled. To make those migrations fast it sets reshardingMinimumOperationDurationMillis and balancerMigrationsThrottlingMs to zero as config server parameters.
However the test also sets replica set parameters which don't include those two resharding/balancer parameters. Under the config shard topology (sharding_config_shard suite) the replica set parameters override the config server parameters, so this test runs slower than expected and can time out.
Suggested fix: Set the same options i.e. (reshardingMinimumOperationDurationMillis and balancerMigrationsThrottlingMs to zero) as both replica sets and config server parameters.
- is caused by
-
SERVER-105874 Improve testing of larger sharded collections from a correctness point of view
-
- Closed
-