[DOCS-16166] Investigate changes in SERVER-66208: Remove chunk creation for shard collection with existing data Created: 29/May/23  Updated: 13/Nov/23  Resolved: 20/Sep/23

Status: Closed
Project: Documentation
Component/s: Server
Affects Version/s: None
Fix Version/s: 6.1.0-rc0, 6.0.3, 7.1.0, 7.0.0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Joseph Dougherty
Resolution: Fixed Votes: 0
Labels: sharding
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-66208 Remove chunk creation for shard colle... Closed
Participants:
Days since reply: 36 weeks, 3 days ago

 Description   
Original Downstream Change Summary

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.


Generated at Thu Feb 08 08:14:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.