-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
ALL
-
v5.1, v5.0, v4.4
-
Repl 2021-11-01
-
45
replsetprio1.js has a race condition when initiating the replset. The nodes are initially configured with different priorities, and when initiating the replset, we add one node at a time by calling replsetReconfig. When adding the third node, there could be a concurrent priority takeover that causes primary node to stepdown and failing replsetReconfig command to fail. As a result, the replset initiation process fails.