[SERVER-6030] Adding member to replica set with down member causes stepDown Created: 07/Jun/12 Updated: 11/Jul/16 Resolved: 02/Sep/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 2.0.5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Colin Howe | Assignee: | Eric Milkie |
| Resolution: | Done | Votes: | 0 |
| Labels: | elections | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
We had the following situation:
We then added a fourth server, D, to the replica set with a view to removing server B afterwards. This caused server A to step down as it no longer had a majority - which is technically accurate. However, I think MongoDB should be smarter than this. We're adding a brand new server - there is no way that the new server should become primary. Alternatively, there should be a warning when adding the new server that the primary will step down and the set will not elect a new primary. |
| Comments |
| Comment by A. Jesse Jiryu Davis [ 02/Sep/14 ] |
|
Could not reproduce with server built from August 25 2014 code, hash e4c72a04f7da. |