-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
Repl 2019-10-21, Repl 2019-11-04
Currently, ReplSetTest.startSet starts up the mongod process for each replica set node serially, one after the other. This process is slow primarily due to the fact that we wait until we can connect to a mongod node before starting up the next one. Instead of waiting until a connection is made to a node before moving on, we can start up all processes in parallel and then wait until connections can be made to each one.
- has to be done before
-
SERVER-44066 Investigate and optimize the slowest portions of ReplSetTest.start when not waiting for a connection
- Closed
- related to
-
SERVER-27342 Do not block unnecessarily on connecting to mongod or finishing initiate in ReplSetTest and ShardingTest
- Closed