-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: 6.0.4, 5.0.15
-
Labels:None
In the collection.drop() documentation we still have a note saying:
For a sharded cluster, if you use db.collection.drop() and then create a new collection with the same name, you must either:
- Flush the cached routing table on every mongos using flushRouterConfig.
- Use db.collection.remove() to remove the existing documents and reuse the collection. Use this approach to avoid flushing the cache.
Running flushRouterConfig after collection drop it is not necessary anymore starting from 5.0. In fact this note have been introduced in DOCS-13703 due to SERVER-17397 that was fixed in 5.0
- is related to
-
-
- Closed
-
-
-
- Closed
-
-
DOCS-13703 drop collection in sharded environments should point out that all mongos instances need cache refreshed
-
- Closed
-