[SERVER-1526] Can't add a new server to a replica set if one of the existing ones is down Created: 30/Jul/10 Updated: 21/Apr/11 Resolved: 21/Apr/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 1.5.6 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Tony Hannan | Assignee: | Dwight Merriman |
| Resolution: | Duplicate | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
db version v1.5.7-pre-, pdfile version 4.5 |
||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
1. Get a replica set running with 2 (or more) servers. |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 21/Apr/11 ] |
|
Fix is |
| Comment by Dwight Merriman [ 24/Aug/10 ] |
|
this page now has some documentation on how to handle minority reconfigurations. this ticket will remain open for future commands that make these things easier. http://www.mongodb.org/display/DOCS/Reconfiguring+a+replica+set+when+members+are+down |
| Comment by Dwight Merriman [ 04/Aug/10 ] |
|
you can now reconfig if a single node is down (and you have a majority) we will generalize this later trying to make change small as close to release. so we'll keep this open but for a future release target. commit c5ca6d00eec9d6b5c636fcd6e9fc85ee3b5a5aa9 |
| Comment by Tony Hannan [ 03/Aug/10 ] |
|
I tested with 3 servers in set with one down and got the same error on rs.add. |
| Comment by Dwight Merriman [ 02/Aug/10 ] |
|
so far it is designed to allow an addition if a majority is up. so not all have to be up, but a majority must be. can you test that case? |