Issuing a movePrimary command should only move unsharded collections, sharded collections are required to be drained first.
Potentially also affects new versions.
Can reproduce easily in a sharded setup, shard a collection, then issue movePrimary to another shard. The first shard will be empty, the second shard will have the data, and the chunks collection will not be updated.
- is duplicated by
-
SERVER-4856 movePrimary should fail if any sharded and undrained collections exists in db
- Closed
-
SERVER-6871 major issues with movePrimary on a non-drained shard
- Closed
-
SERVER-3413 moveprimary doesn't propagate changes to other mongos instances
- Closed