[SERVER-8748] replSetStepDown doesn't acknowledge that hidden nodes cannot become primary Created: 27/Feb/13 Updated: 26/Sep/17 Resolved: 22/Jul/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 2.4.0-rc1 |
| Fix Version/s: | 2.5.2 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Barrie Segal | Assignee: | Scott Hernandez (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Case: | (copied to CRM) | ||||||||
| Description |
|
From docs here:
If replSetStepDown is called in a replica set with no valid new primaries (e.g. secondaries in RECOVERING or hidden nodes), and a hidden node is within 10 seconds of the primary, the primary steps down but a new primary cannot be elected. This results in a replica set consisting of all secondaries. replSetStepDown should throw an error if there is no new primary to be elected, even if another unelectable node is within 10 seconds. |
| Comments |
| Comment by auto [ 23/Jul/13 ] |
|
Author: {u'username': u'scotthernandez', u'name': u'Scott Hernandez', u'email': u'scotthernandez@gmail.com'}Message: |
| Comment by auto [ 22/Jul/13 ] |
|
Author: {u'username': u'scotthernandez', u'name': u'Scott Hernandez', u'email': u'scotthernandez@gmail.com'}Message: |