[SERVER-497] Replacing replica pair node should not require a reboot of master node Created: 18/Dec/09 Updated: 12/Jul/16 Resolved: 18/Aug/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Bob T. Terminal | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 3 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
When the master in a replica pair goes down and needs to be replaced with a new slave node the new existing master should not require a reboot to peer with a new node. For high availability networks the current model will not work. currently model: > db.$cmd.findOne( {replacepeer:1}); |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 18/Aug/10 ] |
|
replica sets fixes this |
| Comment by Kenny Gorman [ 18/Aug/10 ] |
|
This is important to us as well. |