-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Catalog and Routing
-
Fully Compatible
-
CAR Team 2024-01-08, CAR Team 2024-01-22, CAR Team 2024-02-05, CAR Team 2024-02-19
SERVER-81293 "mechanically" replaced all usages of ensurePrimaryShard and marked all the places explicitly setting a primary shard, either by calling enableSharding or movePrimary.
The purpose of this ticket is to change all tests that are using movePrimary to move data from one shard to another as part of the test and are not doing any specific functional or integration test of movePrimary.
- depends on
-
SERVER-81293 Get rid of `ensurePrimaryShard` helper
- Closed
- is depended on by
-
SERVER-83925 movePrimary coordinator should stop cloning unsplittable collections
- Closed
-
SERVER-85524 Re-enable analyze_shard_key_database_and_shard_versioning.js targeting secondaries node
- Closed
-
SERVER-86170 Complete TODO listed in SERVER-86014
- Closed
- is duplicated by
-
SERVER-85524 Re-enable analyze_shard_key_database_and_shard_versioning.js targeting secondaries node
- Closed
-
SERVER-79746 Update config shard tests to use moveCollection
- Closed
-
SERVER-86014 Adapt multi_collection_transaction_placement_conflict_workaround.js for tracked collections
- Closed
- related to
-
SERVER-85650 crud_and_ddl.js should use transitionToDedicated like removeShard
- Closed
-
SERVER-84422 Remove `movePrimary` calls from tests not needing it
- Closed