Kill clone operation of move primary on cleanup

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Catalog and Routing
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              [DO NOT USE] Backlog - Catalog and Routing
              Reporter:
              Marcos José Grillo Ramirez
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: