-
Type: Improvement
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: Backlog
-
Component/s: Sharding
Currently the drop database coordinator is only partially resilient to CSRS/participant stepdowns or network partitions, in fact currently we rely on the retry logic of some other component such as the runCommandWithFixedRetryAttempts function that is retrying just 3 times. The goal of this ticket is to make the drop database coordinator retries all its phases indefinitely until a stepdown happen.
- depends on
-
SERVER-54945 Make drop database resilient to stepdowns on sharded cluster
- Closed
- related to
-
SERVER-56211 Complete TODO listed in SERVER-55396
- Closed
-
SERVER-56495 Complete TODO listed in SERVER-55396
- Closed