[SERVER-85195] enable launching MongoT for sharded cluster deployment Created: 12/Jan/24 Updated: 06/Feb/24 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Maddie Zechar | Assignee: | Backlog - Query Integration |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Query Integration
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
This ticket depends on SERVER-85194 because that ticket will add the MongoTFixture and MongotLauncher classes.
As with SERVER-85194, this ticket will require having a mongot binary locally downloaded to your VM. This ticket will create the new sharded_search_end_to_end suite and a dummy jstest that launches a sharded cluster with a mongot for each mongod.
The constructor for ShardedClusterFixture, will set a flag, launch_mongot, on either self.mongod_options or self.mongos_options to indicate if a mongot process has been requested by the suite's enable_mongot parameter.
In ShardedClusterBuilder::build_fixture(), the launch_mongot flag will be checked and if true, a MongoTFixture will be created per shard with a path to the mongot binary (which will have been specified via –installDir=<path/to/server/artifacts> and parsed by resmoke during setup). In ShardedClusterBuilder::setup(), each MongoTFixture will be setup (ostensibly via calling MongoTFixture::setup() ) In ShardedClusterBuilder::build_fixture(), the launch_mongot flag will be checked and if true, a MongoTFixture will be created per shard with a path to the mongot binary (which will have been specified via –installDir=<path/to/server/artifacts> and parsed by resmoke during setup). In ShardedClusterBuilder::setup() each MongoTFixture will be setup. |