[DOCS-8514] dropDatabase in sharded environments should point out that all mongos instances need cache refreshed Created: 05/Aug/16 Updated: 11/Jun/20 Resolved: 15/Aug/18 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Roy Rim | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Participants: | |||||||||||||
| Days since reply: | 5 years, 26 weeks ago | ||||||||||||
| Epic Link: | DOCSP-1769 | ||||||||||||
| Description |
|
Hey team, after running a dropDatabase and then creating a new database with the same name will leave mongos instances, other than the one that dropped the database, with old information about where the "primary shard" for the database is. Please see We have a warning on movePrimary about mongos concurrency issue and we feel that the same warning should be on dropDatabase. Regards, |
| Comments |
| Comment by Githook User [ 15/Aug/18 ] |
|
Author: {'name': 'kay', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}Message: |
| Comment by Githook User [ 15/Aug/18 ] |
|
Author: {'name': 'kay', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}Message: |
| Comment by Githook User [ 15/Aug/18 ] |
|
Author: {'name': 'kay', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}Message: |