The logic in the sharding balancer policy uses an integer division in order to determine the optimal number of chunks per shard in a cluster. Because of this, the result gets rounded down, which makes the optimal number of chunks in a cluster with 3 chunks and 2 shards to be 1. Because of this, the balancer will move a chunk on each iteration and the cluster will never be deemed "balanced".
Sharding balancer always bounces a single extra chunk if there are less than 20 chunks in total
- Votes:
-
0 Vote for this issue
- Watchers:
-
4 Start watching this issue
- Created:
- Updated:
- Resolved: