[SERVER-27810] Guarantee that replicaset is stable with node 0 as primary after ReplSetTest.initiate() Created: 25/Jan/17 Updated: 05/Apr/17 Resolved: 23/Feb/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.4.3, 3.5.4 |
| Type: | Improvement | 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 | ||||||||||||||||||||
| Backport Requested: |
v3.4
|
||||||||||||||||||||
| Sprint: | Repl 2017-03-06 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Linked BF Score: | 0 | ||||||||||||||||||||
| Description |
|
reconfig can occasionally lead to the primary stepping down. This means that the guarantee we thought |
| Comments |
| Comment by Githook User [ 31/Mar/17 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: This option was removed in (cherry picked from commit 2e189a57db00b291b171d5a2323700d6f57cd471) |
| Comment by Githook User [ 29/Mar/17 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: This option was removed in |
| Comment by Githook User [ 06/Mar/17 ] |
|
Author: {u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}Message: (cherry picked from commit 3823a20f0186d0e6b544212fb423f9f0ef786235) |
| Comment by Githook User [ 23/Feb/17 ] |
|
Author: {u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}Message: |
| Comment by Judah Schvimer [ 06/Feb/17 ] |
|
I actually think these are separate issues. |
| Comment by Crystal Horn [ 03/Feb/17 ] |
|
We should fix this for all repl sets not just ones in the sharding test by fixing |