[DOCS-761] Best Practices on Sharding Large Collections Created: 15/Nov/12 Updated: 15/Apr/13 Resolved: 15/Apr/13 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Mark porter | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Any MongoDB environment. |
||
| Issue Links: |
|
||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Days since reply: | 11 years, 13 weeks, 6 days ago | ||||||||||||||||||||
| Description |
|
Some users have large collections (> 256gb), which cannot be sharded as per the normal sharding process/methodology. You have to write a script to read it and insert into the sharded collection. You then need to blow away the old collection and rename the new collection. The limit is mentioned here but I believe that it should be more explicitly mentioned in the central sharding documentation area along with a process on what can be done. |