Details
-
Bug
-
Resolution: Won't Fix
-
Major - P3
-
None
-
3.5.13
-
None
-
Sharding
-
ALL
Description
The movePrimary command can return a 'it is already the primary' error when the shard it is given to make primary already is the primary.
Now that the movePrimary command is running on the config server, the mongos can return this error when it DOES set a new shard primary successfully. This is because the config server can interrupt the movePrimary command with a step down, say after the config.databases write but before waiting for replication is complete. The mongos then gets a PrimarySteppedDown error from the config server and retries the command to find to find the operation already done.
This is a new behavior in v3.5 because movePrimary runs on the config server now.
Attachments
Issue Links
- related to
-
SERVER-31008 Make trying to move the primary shard to the current primary not return an error
-
- Closed
-