-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Query Integration
-
Fully Compatible
-
QI 2024-02-19, QI 2024-03-04, QI 2024-03-18
-
135
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.
- depends on
-
SERVER-85194 create MongoTFixture and and enable launching Mongot
- Closed
- fixes
-
SERVER-87282 correctly set val of launch_mongot in ReplSetBuilder build_fixture
- Closed
- is depended on by
-
SERVER-85198 create a MongoTFixture for resmoke and enable launching mongot in a single node repl set
- Closed
-
SERVER-85995 track milestone 1
- Closed