-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Replication
-
Fully Compatible
-
ALL
-
0
The replsetprio1.js test has the following 3-node replica set configuration:
Node 0 -> Priority 1
Node 1 -> Priority 2
Node 2 -> Priority 3
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.