rebalancing
Move existing partitions or replicas to improve their placement.
Use this when A newly added shard is idle while older shards carry most data.
without the term
“The new shard is mostly empty while old shards are overloaded. Move existing data without overwhelming the service.”
with the term · How do you ask a model for rebalancing?
Rebalance existing partitions across these nodes. Verify placement constraints, migration load, and per-node traffic.
What is rebalancing?
Rebalancing changes where existing data ranges or replicas live, subject to capacity and placement rules. It need not change the key that assigns records to partitions.
Why does rebalancing matter when vibe coding?
An agent can add a node and expect old data and traffic to move automatically.
How do you do rebalancing?
Inspect bytes, traffic, and replica constraints per node. Move data gradually, then verify placement and request latency. Distinguish balancing bytes from balancing hot keys.
What goes wrong with rebalancing?
Moving an indivisible hot key to another node can merely move the bottleneck.
Sources for this entry
- MongoDB: Sharded cluster balancer
The balancer migrates data ranges between shards subject to placement constraints.
- MongoDB: Reshard a collection
Resharding can change the shard key or force redistribution; it has resource and write-blocking requirements.
Sources checked . Source checks do not establish human editorial approval. How we check content.