[DOCS-3154] Sharding limitation needs a "Contact MongoDB" instruction Created: 14/Apr/14 Updated: 11/Jan/17 Resolved: 18/Apr/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | mongodb-2.6 |
| Fix Version/s: | 01112017-cleanup |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Joe Drumgoole (Inactive) | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 9 years, 44 weeks, 2 days ago | ||||||||
| Description |
|
On this page : http://docs.mongodb.org/manual/reference/limits/#limits-sharding We quote the following limitation: Sharding Existing Collection Data Size IMPORTANT We don't really explain the rational for this limitation nor do we give any guidance as to what a customer should do if they find themselves in this situation. Might be worth suggesting they contact MongoDB if they find themselves in this situation. |