-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Sharding EMEA
-
Fully Compatible
-
Sharding EMEA 2023-07-24, Sharding EMEA 2023-08-07, Sharding EMEA 2023-10-02, Sharding EMEA 2023-10-16, Sharding EMEA 2023-10-30
Following the removal of the auto-splitter in versions >= v6.0.3, balancing does not happen anymore on number of chunks but on actual data size and the balancer is issuing moveRange commands (DOCS-15363) to atomically split+move subparts of a chunk.
Purpose of this ticket is to change the default behavior for creating/distributing chunks when sharding an empty collection with hashed shard key: one chunk per shard, in line with the decision taken also for resharding (SERVER-68050).
- is related to
-
SERVER-82068 Investigate handling of MinKey and MaxKey in moveChunkParallel helper
- Open
-
SERVER-81884 Get rid of featureFlagOneChunkPerShardEmptyCollectionWithHashedShardKey once v8.0 branches out
- Open
-
SERVER-82216 Make a more even distribution of chunks through shards for initial split policies with zones
- Backlog
-
SERVER-74747 Deprecate `numInitialChunks` parameter of `shardCollection` command
- Closed