-
Type: Task
-
Resolution: Won't Do
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
None
-
Catalog and Routing
SERVER-81229 fix the correctness issue of move primary on stepdown, however, we still might have a clone operation that could take hours, which is unacceptable from an user perspective.
The purpose of this ticket is to investigate and implement a kill of the clone operation on the cleanup phase before dropping any leftover collection from a previous coordinator incarnation.
- is related to
-
SERVER-81229 Move primary may not cleanup cloned collections on failure
- Closed