[SERVER-59939] Create javascript test fixture for serverless topology Created: 14/Sep/21  Updated: 06/Dec/22  Resolved: 19/Nov/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Janna Golden Assignee: [DO NOT USE] Backlog - Server Serverless (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-59949 Create serverless test suite Closed
Duplicate
duplicates SERVER-61464 Make all tests in jstests/serverless ... Closed
Gantt Dependency
Assigned Teams:
Serverless
Participants:

 Description   
  • Using the ShardingTest javascript fixture (shell/shardingtest.js) as a base, create a new js test fixture that starts up the server side components of a serverless pod. For the purposes of this ticket, the components should be one or mongoqd, one config server, and one or more replica sets started up as shard servers (the number of mongoqds and replica sets should be configurable as they are in ShardingTest). Note that as a part of PM-2347, we should change these components to be in line with the longer term serverless architecture.
    • The serverless fixture shouldn't need most of the functions specific to sharding/sharded collections defined in shardingtest.js i.e. anything related to mongos, and functions such as`chunkCounts`, `awaitBalancerRound`, and `shardColl`.
    • The balancer should be stopped and auto split turned off. Serverless will not rely on the balancer to move data.
  • The documentation in shardingtest.js is lacking, let's make the documentation for this fixture more robust, including providing TypeScript typings.

Generated at Thu Feb 08 05:48:34 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.