[SERVER-2253] db.dropDatabase is not erasing the database entry from the configdb Created: 20/Dec/10 Updated: 12/Jul/16 Resolved: 30/Aug/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 1.9.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Alberto Lerner | Assignee: | Greg Studer |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Participants: | |||||||||||||||||
| Comments |
| Comment by Greg Studer [ 29/Aug/11 ] |
|
Need to backport |
| Comment by Greg Studer [ 29/Aug/11 ] |
|
git commmit is a2714c023c1e054708a7f66ff0b66856573fbd3a |
| Comment by Greg Studer [ 04/Aug/11 ] |
|
Workaround is to manually drop the db from the config database **AFTER** dropping the sharded db from the shell via **mongos**: mongo <mongos instance> ) |
| Comment by auto [ 20/Dec/10 ] |
|
Author: {u'login': u'alerner', u'name': u'Alberto Lerner', u'email': u'alerner@10gen.com'}Message: |
| Comment by auto [ 20/Dec/10 ] |
|
Author: {u'login': u'alerner', u'name': u'Alberto Lerner', u'email': u'alerner@10gen.com'}Message: |