-
Type: Bug
-
Resolution: Fixed
-
Priority: Minor - P4
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
ALL
-
Repl 2019-11-18
-
21
The jstests/replsets/reconfig.js does a force reconfig to remove the last node of a 5 node replica set and then calls ReplSetTest.stopSet. If the last node transitions to REMOVED state (because it received a heartbeat with the new config) while we are trying to validate collections on that node inside stopSet, we can run into an error because the node is not in primary or secondary state. Since the test has already finished testing the necessary aspects of reconfig by the end, we can add the node back into the set before stopping the test to avoid this issue.
- related to
-
SERVER-39172 Shut down mongod nodes in parallel in ReplSetTest
- Closed