[SERVER-27365] reconfig_without_increased_queues.js should initiate node 2 of its replicaset with priority 0 Created: 09/Dec/16 Updated: 05/Apr/17 Resolved: 17/Jan/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 3.2.11, 3.4.0, 3.5.1 |
| 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 first reconfig will fail if node 2 is randomly elected at the start of the test. |
| Comments |
| Comment by Githook User [ 19/Jan/17 ] |
|
Author: {u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}Message: (cherry picked from commit 686069d0fbde93c1bf8b2fe15fad001e98dcc25d) |
| Comment by Githook User [ 19/Jan/17 ] |
|
Author: {u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}Message: (cherry picked from commit 686069d0fbde93c1bf8b2fe15fad001e98dcc25d) |
| Comment by Githook User [ 17/Jan/17 ] |
|
Author: {u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}Message: |
| Comment by Spencer Brody (Inactive) [ 12/Dec/16 ] |
|
Yep, good point. Can probably do something like the write_concern_after_stepdown.js test does. |
| Comment by Judah Schvimer [ 12/Dec/16 ] |
|
This fix needs to be backported to 3.2 where stepUp is not available. Alternatively to stepUp, we could check if node 2 is the primary and if so we could step it down before calling reconfig. |
| Comment by Spencer Brody (Inactive) [ 10/Dec/16 ] |
|
What if instead we called stepUp on the node that the test expects to be primary? Just to avoid introducing priorities into tests that don't need them, since they can cause their own kinds of flakiness. |