[DOCS-6969] Instructions for migrating MMAP -> WT do not describe the option of using "initial sync" Created: 13/Jan/16 Updated: 11/Jan/17 Resolved: 13/Jan/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Mark Brinsmead | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 8 years, 5 weeks ago | ||||||||
| Description |
|
The MMAP -> WT migration instructions describe an upgrade method based on mongodump and mongorestore. Customers with replicasets are likely to find an initial sync (with the "automatic" method) preferable in many instances. A strict reading of the documentation might lead one to believe that mongodump is the only method available. |
| Comments |
| Comment by Kay Kim (Inactive) [ 13/Jan/16 ] |
|
Works as designed in that each upgrade section has its own mmapv1-> wt section, however, as noted in the other comment, we're in the middle of separating out the mmapv1->wt procedures from the upgrade page which would make it clear that there are different procedures available. |