-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
ALL
-
v3.4, v3.2
-
Repl 2017-01-23
-
0
The test does a reconfig to make node 0 have priority 0 which fails if node 0 is primary then. We could make the test not care which node is primary after that point, but it'll lead to a more confusing and longer test. The easier solution would be to just add one more stepDown if node 0 is primary at that point.