-
Type:
Task
-
Resolution: Duplicate
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing, Correctness
-
3
As a preliminary step for replacing ShardingTest-based passthrough suites with JS core suites based on ShardedClusterFixture, we should address the existing test coverage gap between the two environments.
In particular, there is currently no equivalent JS core passthrough suite for:
un/sharded clustered collections (buildscripts/resmokeconfig/suites/sharding_clustered_collections.yml)addressed through SERVER-100775sharded clusters with data encryption enabled (sharding_ese and similar overrides)addressed throughSERVER-93436mongos nodes with opportunisticSecondaryTargeting enabled (sharding_opportunistic_secondary_targeting and related overrides)addressed through SERVER-94391mongod nodes with maxed settings for mirrored reads (sharding_max_mirroring and related overrides)addressed through SERVER-100776.
- duplicates
-
SERVER-100776 Ensure code coverage for mongod nodes with maxed mirrored read settings within the JS core framework
-
- Backlog
-
-
SERVER-94391 Delete sharding_max_mirroring_opportunistic_secondary_targeting
-
- Blocked
-
-
SERVER-93436 Replace _ese and _ese_gcm variations of replica_sets and sharding with config fuzzer
-
- Closed
-
-
SERVER-100775 Ensure code coverage for un/sharded, non-timeseries clustered collections within the JS core framework
-
- Needs Scheduling
-
- is depended on by
-
SERVER-97430 Add an evergreen task to ban the addition of new files within jstests/sharding
-
- Blocked
-