[DOCS-13703] drop collection in sharded environments should point out that all mongos instances need cache refreshed Created: 11/Jun/20 Updated: 30/Oct/23 Due: 04/Sep/20 Resolved: 01/Sep/20 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Nic Cottrell | Assignee: | Jason Price |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | bite-sized, docs-administration | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Days since reply: | 3 years, 23 weeks, 1 day ago | ||||||||||||||||
| Epic Link: | DOCSP-1769 | ||||||||||||||||
| Description |
DescriptionSimilar to 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 changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Githook User [ 01/Sep/20 ] |
|
Author: {'name': 'Jason Price', 'email': 'jason.price@mongodb.com', 'username': 'jason-price-mongodb'}Message: |
| Comment by Githook User [ 01/Sep/20 ] |
|
Author: {'name': 'Jason Price', 'email': 'jason.price@mongodb.com', 'username': 'jason-price-mongodb'}Message: |
| Comment by Githook User [ 01/Sep/20 ] |
|
Author: {'name': 'Jason Price', 'email': 'jason.price@mongodb.com', 'username': 'jason-price-mongodb'}Message: |
| Comment by Githook User [ 01/Sep/20 ] |
|
Author: {'name': 'Jason Price', 'email': 'jason.price@mongodb.com', 'username': 'jason-price-mongodb'}Message: |