Part 1 of 5 · 1 min read
Why this page comes first
In this module you will
- Explain why adding or removing nodes requires moving existing data between partitions.
- Compare automatic and manual rebalancing.
- Explain why rebalancing without downtime requires careful, incremental data movement.
- Judge whether a described rebalancing plan risks unnecessary disruption.
The previous two pages assumed a fixed number of partitions. This page covers what happens when that number changes. A node is added for more capacity, or removed after a failure, and existing data must be redistributed to match.