-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Server
-
Labels:
When sharding a non-empty collection, we only create one giant chunk on the db primary shard.
Since we do not rely anymore on splitVector, sharding a collection is not subject anymore to the size limitation described in https://www.mongodb.com/docs/manual/reference/limits/#mongodb-limit-Sharding-Existing-Collection-Data-Size
Description of Linked Ticket
The UnoptimizedSplitPolicy for initial chunk creation chooses how many chunks to create using AutoSplitVector and creates all chunks on the primary shard. After disabling the autosplitter, it no longer makes sense to split the collection into chunks on a single shard for the initial split policy.
After removing the autosplitter, we should just create a single chunk on the primary shard.
- documents
-
SERVER-66208 Remove chunk creation for shard collection with existing data
- Closed