Every mongos instance starts a balancer round every few seconds. While looking for candidate chunks to move, it always reads all of the chunks with the given ns from the config database, many times only to realize that the collection is in fact well balanced. This may cause a significant network load.
- depends on
-
SERVER-22672 Move the sharding balancer to CSRS primary
-
- Closed
-
- is duplicated by
-
SERVER-14810 Balancer shouldn't need to load the full config.chunks every time
-
- Closed
-