-
Type:
Bug
-
Resolution: Won't Fix
-
Priority:
Major - P3
-
None
-
Affects Version/s: 3.2.18, 3.4.10, 3.6.0, 3.7.1
-
Component/s: Sharding
-
Sharding
-
ALL
-
27
If a movePrimary command was able to clone the database but failed to complete (for example, because it stepped down), it will leave the database and the other collections in the original shard. Attempting to call the command again will do nothing because the primary database is now officially moved to the another shard, leaving the unsharded collections orphaned on the old primary shard.
There's also another variant where it fails after it successfully clones, but before it updates config.databases. In this scenario, attempting to retry to command will result in the command attempting to call clone again, but fail with collection already exits.
- is related to
-
-
- Closed
-
- related to
-
-
- Backlog
-
-
-
- Closed
-