-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Critical - P2
-
None
-
Affects Version/s: 2.2.1, 2.4.0-rc1
-
Component/s: Sharding
-
Labels:None
-
ALL
-
We moved an (unsharded) database from one shard to another using movePrimary command and following the instructions here:
Having done that users starting complaining of unauthorized access. Sure enough connecting to their local mongos showed that the database that had been moved, and the system.users collection within it, were empty. I.e. the mongos didn't pick up the fact that the database had moved.
This is somewhat worrying, and essentially required us to restart mongos' across the cluster. This makes us worry that, if a process had auth (to admin say) they would be writing to the wrong shard for that database - and we'd experience data loss. It's also worrying that mongoses don't appear to automatically pick up changes like this.
- duplicates
-
SERVER-8059 After movePrimary, db.getCollectionNames() excludes previously existing one-chunk collections
-
- Closed
-
- is duplicated by
-
SERVER-16024 listCollections is missing collections if primaryShard is moved
-
- Closed
-
- is related to
-
SERVER-7394 'movePrimary' should issue a warning if data exists in the database being moved
-
- Closed
-
-
SERVER-939 Ability to distribute collections in a single db
-
- Closed
-