[SERVER-1829] Initial replica set sync should clone from secondary Created: 22/Sep/10 Updated: 12/Jul/16 Resolved: 08/Dec/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 1.7.4 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | David Mytton | Assignee: | Kristina Chodorow (Inactive) |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
When you add a new member to a replica set (or need to resync an existing member), it clones the data from the primary. This causes a performance impact. Instead, it would be better if the initial clone was take from a secondary so only the catchup running through the oplog need take place on the primary. |
| Comments |
| Comment by auto [ 17/Nov/10 ] |
|
Author: {'login': 'kchodorow', 'name': 'Kristina Chodorow', 'email': 'kristina@10gen.com'}Message: lots of options for initial sync |
| Comment by auto [ 09/Nov/10 ] |
|
Author: {'login': 'kchodorow', 'name': 'Kristina Chodorow', 'email': 'kristina@10gen.com'}Message: allow initial sync from secondaries |
| Comment by Dwight Merriman [ 05/Nov/10 ] |
|
kristina maybe you can do this one - although we have some other things to do first... |
| Comment by Dwight Merriman [ 05/Nov/10 ] |
|
agreed. we will do that in the future. a workaround for now would be to start the new member with a complete set of datafiles from a backup from an existing set member. then it will start from what it has. I have not tried this recently, it is possible it will "complain" at first that it isn't a member of the set (as it will start before being added) but other than that possibility, it would work fine, as there is nothing in the datafiles unique to a particular member the way replica sets are designed. |