-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Fully Compatible
-
ALL
-
v7.0, v6.3, v6.0
-
Sharding EMEA 2022-11-14, Sharding EMEA 2022-11-28, Sharding EMEA 2022-12-12, Sharding EMEA 2022-12-26, Sharding EMEA 2023-01-09, Sharding EMEA 2023-01-23, Sharding EMEA 2023-02-06, Sharding EMEA 2023-02-20, Sharding EMEA 2023-03-06, Sharding EMEA 2023-03-20, Sharding EMEA 2023-04-03, Sharding EMEA 2023-04-17
-
5
On every balancer round, the balancer iterates over all the sharded collections stopping when all shards are already involved in one migration (SERVER-70973).
However, the balancer can still exceed the 1 sec defined interval time between rounds (kBalancerMigrationsThrottling) in the following scenarios:
- The number of sharded collections is very high and it's not possible to involve all shards in a migration.
- The number of sharded collections is very high and just a few of them are imbalanced.
- causes
-
SERVER-76172 Fix BalancerChunkSelection unit test on slow build variants
- Closed
- depends on
-
SERVER-68670 Cache imbalanced collections for balancing
- Closed