[DOCS-13023] [Server] Explain why chunkSize is divided by two in Limits > Sharding Existing Collection Data Size Created: 06/Sep/19 Updated: 30/Oct/23 Resolved: 21/Jul/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | 4.2.0 |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Kevin Arhelger | Assignee: | Nick Villahermosa |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | quick-win, server-docs-bug-bash | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 28 weeks, 5 days ago |
| Description |
Descriptionhttps://docs.mongodb.com/manual/reference/limits/#Sharding-Existing-Collection-Data-Size
I believe this two stems from the fact that initial chunks will be half full when created. Explaining this would better help users understand how many chunks to expect when sharding a collection. Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Nick Villahermosa [ 21/Jul/23 ] |
|
Backports: 6.3, 6.0, 5.0, 4.4 |