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

_configsvrMovePrimary retries fail if clone from old primary completed in a previous attempt

    XMLWordPrintable

Details

    • ALL
    • 26

    Description

      If the CSRS primary steps down while executing _configsvrMovePrimary after having told the toShard to clone the non-sharded collections from the old primary shard, the clone will still complete because the shards won't know the command was interrupted, but mongos will receive a retryable error and retry _configsvrMovePrimary when the next primary steps up, because it uses RetryPolicy::kIdempotent. When the new primary sends the clone command to the toShard again, the clone will fail, because the namespaces to be cloned will already exist on the toShard, causing the whole command to fail (unless there weren't any unsharded collections).

      Attachments

        Issue Links

          Activity

            People

              backlog-server-sharding Backlog - Sharding Team
              jack.mulrow@mongodb.com Jack Mulrow
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: