-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Catalog and Routing
-
Fully Compatible
-
v8.0
-
CAR Team 2024-05-13, CAR Team 2024-05-27, CAR Team 2024-06-10, CAR Team 2024-06-24, CAR Team 2024-07-08
-
200
When removing a shard, we take a lock on all things (coll/db) on that shard, Check that that shard doesn’t own any collection data or database, then commit the removeShard.
Test of checkMetadataConsistency before (or after) decommissioning a shard.
This ticket is for https://github.com/mongodb/mongo/blob/master/buildscripts/resmokeconfig/suites/concurrency_sharded_replication_with_balancer_and_config_transitions.yml - removeshard version. Once this is done, we can try to enable a terminate/stepdown version in a different ticket
- depends on
-
SERVER-90224 Run sharding metadata consistency checks after ContinuousConfigShardTransition hook completes a transition
- Closed
-
SERVER-90225 TransitionToDedicated/removeShard extra consistency checks
- Closed
-
SERVER-90377 Update existing configTransitions to use for add/removeShard(de-comissioning)
- Closed
- is depended on by
-
SERVER-91879 Add ShardNotFound to allowed errors in the abortTransaction helper
- Closed