Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-40859

Orphaned collections after a movePrimary that fails to cleanup can cause future migrations to fail

XMLWordPrintableJSON

    • Sharding EMEA
    • ALL
    • 0

      If the movePrimary command is interrupted after it successfully runs configsvrCommitMovePrimary but before it finishes dropping all the cloned collections, they can cause errors when chunks for those collections eventually get moved to this shard. This is because movePrimary assigns new UUID to the cloned collections and the UUIDs for the "orphaned" collections and the new sharded collections will be different.

            Assignee:
            backlog-server-sharding-emea [DO NOT USE] Backlog - Sharding EMEA
            Reporter:
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: