[DOCS-4841] Provide clear warning documentation that users cannot be upgraded between 2.4 and 2.6 by dump and restore Created: 17/Feb/15 Updated: 11/Jan/17 Resolved: 18/Feb/15 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Task | Priority: | Critical - P2 |
| Reporter: | David Hows | Assignee: | Michael Paik |
| 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, 1 day ago | ||||||||||||
| Description |
|
If you attempt to mongodump and database with users from MongoDB 2.4 and restore it to MongoDB 2.6 there is no simple upgrade path for the users. We should have clear warnings in the mongorestore/mongodump page and the upgrade process page about this limitation. Ideally we should also have a workaround procedure in the docs to assist end users. |