[DOCS-14922] Review "Sharding Existing Collection" section Created: 10/Nov/21  Updated: 13/Nov/23  Resolved: 02/Feb/22

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 5.0.0, 5.1.0, 5.2.0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Joseph Dougherty
Resolution: Works as Designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Participants:
Days since reply: 2 years, 1 week ago
Epic Link: DOCSP-17171

 Description   

The documentation added in DOCS-7145 has become stale after the commit of SERVER-59806.

Hence the following section should be deleted when the backports linked to this ticket will be completed:
https://docs.mongodb.com/manual/core/sharded-cluster-requirements/#sharding-existing-collection-data-size



 Comments   
Comment by Pierlauro Sciarelli [ 02/Feb/22 ]

Hi Joseph, reading the code committed under SERVER-59806 I realized that the limits actually still apply: while it's possible to commit an unlimited number of chunks at collection sharding time, the output of the function retrieving the split points is still capped to 16MB.

Sorry for the unnecessary buzz!

Comment by Joseph Dougherty [ 02/Feb/22 ]

pierlauro.sciarelli Thanks for opening this issue. Are there any limits that users need to be aware of, or are there no size limits for sharding an existing collection?

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