[SERVER-27342] Do not block unnecessarily on connecting to mongod or finishing initiate in ReplSetTest and ShardingTest Created: 08/Dec/16 Updated: 06/Dec/22 Resolved: 02/Oct/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Sharding, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Backlog - Replication Team |
| Resolution: | Duplicate | Votes: | 2 |
| Labels: | tig-mongorunner | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Assigned Teams: |
Replication
|
||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Description |
|
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. |
| Comments |
| Comment by William Schultz (Inactive) [ 02/Oct/19 ] |
|
Deciding to close this issue and break it up into smaller subtasks as a part of PM-1360. See the following tickets: |