Clean up orphaned collections on recipient after movePrimary failure

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 6.3.0-rc0
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • Sharding EMEA 2022-12-26, Sharding EMEA 2023-01-09, Sharding EMEA 2023-01-23
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In case of a failure of a movePrimary operation, dirty data (partially or fully cloned) could remain on the recipient node, causing a persistent failure of any subsequent movePrimary operation attempts (NamespaceExists error).

      In order to recover, a manual drop operation of this dirty data is required on the recipient node.

            Assignee:
            Antonio Fuschetto
            Reporter:
            Antonio Fuschetto
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: