Details
-
Bug
-
Resolution: Duplicate
-
Major - P3
-
None
-
None
-
None
-
ALL
Description
The new shard for a database on movePrimary is not propagated to mongos automatically - this should trigger a StaleConfigException on a sharded connection.
Attachments
Issue Links
- related to
-
SERVER-4262 when dropping collections need to invalidate all conn sharding state
-
- Closed
-