[SERVER-27656] Ensure node 0 is not primary during reconfig in last_vote.js Created: 12/Jan/17 Updated: 05/Apr/17 Resolved: 18/Jan/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.12, 3.4.2, 3.5.2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Judah Schvimer |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v3.4, v3.2
|
||||||||
| Sprint: | Repl 2017-01-23 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
The test does a reconfig to make node 0 have priority 0 which fails if node 0 is primary then. We could make the test not care which node is primary after that point, but it'll lead to a more confusing and longer test. The easier solution would be to just add one more stepDown if node 0 is primary at that point. |
| Comments |
| Comment by Githook User [ 24/Jan/17 ] |
|
Author: {u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}Message: (cherry picked from commit 2ff3efcabb0a43d5d21b3d636caa76efa4df8bd3) |
| Comment by Githook User [ 20/Jan/17 ] |
|
Author: {u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}Message: (cherry picked from commit 2ff3efcabb0a43d5d21b3d636caa76efa4df8bd3) |
| Comment by Githook User [ 18/Jan/17 ] |
|
Author: {u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}Message: |