-
Type:
Bug
-
Status: Closed
-
Priority:
Major - P3
-
Resolution: Fixed
-
Affects Version/s: None
-
Component/s: Replication
-
Labels:None
-
Backwards Compatibility:Fully Compatible
-
Operating System:ALL
-
Backport Requested:v3.4, v3.2
-
Linked BF Score:0
The test occasionally fails because the high priority node steps up before the low priority node is elected. We can increase the stepDownGuard in priority_takeover_one_node_higher_priority.js to 10 * electionTimeoutMillis, then explicitly end the stepdown period on the high priority node with replSetFreeze after the low priority node is elected to avoid the test taking longer.