[SERVER-31940] replsetprio1.js should use initiateWithAnyNodeAsPrimary Created: 13/Nov/17 Updated: 30/Oct/23 Resolved: 13/Nov/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.0-rc4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | William Schultz (Inactive) | Assignee: | Backlog - Replication Team |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Replication
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
The replsetprio1.js test has the following 3-node replica set configuration: Node 0 -> Priority 1 When we start the test, we call ReplSetTest#initiate which tries to wait for node 0 to become primary. We should be allowing any node to become primary initially, so we don't cause unexpected election failures by trying to step up a node with the lowest priority in a replica set. This test doesn't rely on the fact that node 0 becomes primary first, so it shouldn't matter if we change this behavior. |
| Comments |
| Comment by Githook User [ 13/Nov/17 ] |
|
Author: {'name': 'William Schultz', 'username': 'will62794', 'email': 'william.schultz@mongodb.com'}Message: |