-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
-
Sharding 2021-02-22, Sharding 2021-03-08
The new drop collection procedure for sharded cluster (introduced in SERVER-52809) is not resilient yet to shutdown of the coordinator shard. This ticket is to implement the coordinator as a PrimaryOnlyService to add such resiliency.
- depends on
-
SERVER-43892 ShardedClusterFixture always starts shards as replicasets
- Closed
-
SERVER-52809 Implement the new drop collection path in _shardsvrDropCollection
- Closed
-
SERVER-54077 Introduce ForwardableOperationMetadata class for DDL operations
- Closed
- is depended on by
-
SERVER-54587 Make create collection resilient to stepdowns
- Closed
-
SERVER-54605 Make rename collection coordinator resilient to stepdowns
- Closed
-
SERVER-54696 Serialize DDL operations on step-up
- Closed
-
SERVER-54944 Make drop collection resilient to stepdowns
- Closed
-
SERVER-54946 Make rename collection resilient to stepdowns
- Closed
-
SERVER-55387 Expose completion future in ShardingDDLCoordinator
- Closed
- is duplicated by
-
SERVER-51755 Introduce a sharding serializer for collection DDL coordinators
- Closed
-
SERVER-52755 Introduce a sharding serializer for database DDL coordinators
- Closed
- related to
-
SERVER-54798 Complete TODO listed in SERVER-53905
- Closed