Provide remediation plan when `moveCollection` does not work for collection residing on its db primary

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When an unsharded collection is residing on the primary shard and is tracked as unsplittable, movePrimary is not going to move it out.

      Purpose of this ticket is to provide a remediation plan when moveCollection is not working (e.g. for bugs that may arise, such as SERVER-89342) so that users can still be able to drain a primary and move away all unsharded collections.

      One way could be relying on the untracking machinery added under SERVER-86311.

              Assignee:
              Unassigned
              Reporter:
              Pierlauro Sciarelli
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: