-
Type: Improvement
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication, Sharding, Testing Infrastructure
-
Replication
ReplSetTest starts up multiple mongods and ShardingTest starts up multiple ReplSetTest's but each are done serially. Test startup could probably be sped up significantly by doing some of this work in parallel. Rather than truly doing this in parallel, we can simply delay connecting to each node until we've started up all of the nodes in a ReplSetTest. Similarly, we can delay calling "awaitSecondaryNodes()" for each ReplSetTest until we've called initiate on each ReplSetTest. This allows most of startup and initiate to be done in parallel both within one ReplSetTest and among multiple ReplSetTests in a ShardingTest.
- is related to
-
SERVER-43772 Start up mongod replica set nodes in ReplSetTest.startSet in parallel
- Closed
-
SERVER-43773 ShardingTest should run the startup procedure for all of its ReplSetTest shard instances in parallel
- Closed
-
SERVER-43774 ShardingTest should initiate all of its ReplSetTest shard instances in parallel
- Closed
-
SERVER-39112 Primary drain mode can be unnecessarily slow
- Closed
-
SERVER-39172 Shut down mongod nodes in parallel in ReplSetTest
- Closed
- related to
-
SERVER-32052 Update ShardingTest to default to starting shard servers as single-node replica sets rather than standalones
- Closed