[SERVER-18831] Reset replication while online Created: 04/Jun/15 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 3.0.3 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Neal Rigney | Assignee: | Backlog - Replication Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Replication
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
A customer would like to be able to reset a replicaset member's local DB while the server remains online. Specifically, assuming the server started in replSet1, would would like to: Because we use mongod embedded in another product, it is not possible for us to make these changes offline. |
| Comments |
| Comment by Andy Schwerin [ 04/Jun/15 ] |
|
I think the only thing you couldn't do today is change the replica set name. Using force reconfig, you should be able to forcibly remove the node of interest from the first set, and make it the only member of a new set of the same name. Then, you could add other nodes to that new set. I think all that's missing is letting you change the replica set name as part of a force reconfig. |
| Comment by Eric Milkie [ 04/Jun/15 ] |
|
The ability to make online changes to replication is not an unreasonable request, but it won't be something we'll have time to work on in the near future. |