When dropping sharded collections on mongod, we need to invalidate all connection state for that namespace. If the collection gets recreated, this information will be stale.
- depends on
-
SERVER-5918 invalid memory writes in sharding test suite
- Closed
- is depended on by
-
SERVER-5150 drop collection : now errors with sharding
- Closed
- is duplicated by
-
SERVER-5753 Assertion failures when a sharded collection is dropped and sharded again and reused.
- Closed
- is related to
-
SERVER-4429 When moving primary need to inform all other mongoses
- Closed