Details
-
Task
-
Status: Closed
-
Major - P3
-
Resolution: Fixed
-
None
-
None
-
None
-
None
-
true
-
(copied to CRM)
Description
Hey team,
after running a dropDatabase and then creating a new database with the same name will leave mongos instances, other than the one that dropped the database, with old information about where the "primary shard" for the database is. Please see SERVER-15213.
We have a warning on movePrimary about mongos concurrency issue and we feel that the same warning should be on dropDatabase.
Regards,
Roy Rim
Attachments
Issue Links
- is related to
-
SERVER-17397 Dropping a Database or Collection in a Sharded Cluster may not fully succeed
-
- Closed
-
-
DOCS-13703 drop collection in sharded environments should point out that all mongos instances need cache refreshed
-
- Closed
-