Details
-
Task
-
Status: Closed
-
Major - P3
-
Resolution: Fixed
-
None
-
None
-
ServerDocs2020: Aug24 - Aug31, ServerDocs2020: Aug31 - Sep07
-
(copied to CRM)
Description
Description
Similar to DOCS-8514 dropping a collection and then reusing the name to create another collection in a sharded environment can lead to stale cache SERVER-17397
https://docs.mongodb.com/manual/reference/method/db.collection.drop/ should warn that dropping and reusing a collection name requires complex cache flushing
Alternatively the docs could add that to avoid this problem, use remove({}) instead and manually drop any unneeded collections.
Scope of changes
Impact to Other Docs
MVP (Work and Date)
Resources (Scope or Design Docs, Invision, etc.)
Attachments
Issue Links
- related to
-
DOCS-15797 Remove deprecated note for collection.drop()
-
- Closed
-
-
SERVER-17397 Dropping a Database or Collection in a Sharded Cluster may not fully succeed
-
- Closed
-
-
DOCS-8514 dropDatabase in sharded environments should point out that all mongos instances need cache refreshed
-
- Closed
-