[SERVER-43776] ShardingTest should run the stop procedure for all of its ReplSetTest shard instances in parallel Created: 02/Oct/19 Updated: 29/Oct/23 Resolved: 08/Aug/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | William Schultz (Inactive) | Assignee: | Kruti Shah |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng, sharding-nyc-subteam2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Repl 2019-12-16, Sharding 2021-08-09, Sharding 2022-07-11, Sharding 2022-07-25, Sharding 2022-08-08, Sharding 2022-08-22 | ||||||||
| Participants: | |||||||||
| Description |
|
Currently, ShardingTest calls stopSet on each of its shard ReplSetTest instances serially. This means that it is not possible to be stopping processes from multiple shards at the same time. To make this stop procedure faster when there are many shards, ShardingTest can stop all ReplSetTest instances at the same time, without waiting for one to complete before moving on to the next one. It can then wait for all shard stop procedures to finish. This will allow the stopping of all shard ReplSetTest instances to proceed in parallel.
|
| Comments |
| Comment by Githook User [ 04/Aug/22 ] |
|
Author: {'name': 'Kruti Shah', 'email': 'kruti139@gmail.com', 'username': 'krutishah139'}Message: |
| Comment by Githook User [ 19/Jul/22 ] |
|
Author: {'name': 'Abdul Qadeer', 'email': 'abdul.qadeer@mongodb.com', 'username': 'zorro786'}Message: Revert " |
| Comment by Githook User [ 14/Jul/22 ] |
|
Author: {'name': 'Kruti Shah', 'email': 'kruti139@gmail.com', 'username': 'krutishah139'}Message: |