[DOCS-6857] Alternative procedure for Initial Sync when moving from MMAPv1 to WT Created: 21/Dec/15 Updated: 30/Oct/23 Resolved: 20/Jan/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | tools |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Dmitry Agranat | Assignee: | Kyle Suarez |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Participants: | |||||||||||||
| Days since reply: | 8 years, 8 weeks, 2 days ago | ||||||||||||
| Description |
|
Hi, When customers want to update a Replica Set member to use the WiredTiger storage engine in a rolling manner, they need to remove the member's data and perform an initial sync. Unfortunately, this will might take many days for customers with large data sets, for example, 5-10TB of data. |