[SERVER-9133] Alternate Resync Method Created: 26/Mar/13 Updated: 06/Dec/22 Resolved: 23/Aug/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | David Hows | Assignee: | Backlog - Replication Team |
| Resolution: | Won't Fix | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Replication
|
||||
| Participants: | |||||
| Description |
|
Can we add an automated method into Mongo which will automate the copy and transfer of the whole dbpath to a new node that is being synchronized. The idea would be similar to creating an "under the hood" version of copying the dbpath between two servers. This will be an optional sync method and would need to be activated by users. |
| Comments |
| Comment by Spencer Brody (Inactive) [ 23/Aug/18 ] |
|
We don't plan on doing this within the server, though it is possible to do externally |
| Comment by Eliot Horowitz (Inactive) [ 26/Mar/13 ] |
|
This would be quite challenging to do generically safely, but we are doing a lot of working making initial sync faster. |