[SERVER-5975] Add option to replSetReconfig to tell it that a new node being added already has a copy of the data Created: 31/May/12 Updated: 15/Aug/12 Resolved: 01/Jun/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Description |
|
A common use case is taking a snapshot of production and using that to seed a staging environment. The problem is that the snapshot contains the replica set configuration for the production machines, not the hosts of the staging environment. Currently, if you bring up the staging environment from the snapshots and try to run replSetReconfig on one to give it the new configuration for the staging environment, the command fails complaining that the other nodes being added to the set already have data on them. If we had this option, we could tell the command to trust that the other nodes have a valid copy of the data, and skip the initial sync phase (possibly after some verification that the oplogs are the same). |
| Comments |
| Comment by auto [ 07/Jun/12 ] |
|
Author: {u'login': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |
| Comment by Spencer Brody (Inactive) [ 01/Jun/12 ] |
|
This already works if you use {force:true} |
| Comment by Scott Hernandez (Inactive) [ 31/May/12 ] |
|
Pretty sure this works with a forced reconfigure. If not, that is a bug. |