[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:
Depends
is depended on by SERVER-1726 drop/dropDatabase concurrency when sh... Closed
Related
is related to SERVER-3205 Dropping sharded database leads to er... Closed
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>
> use config
> db.databases.remove(

{ _id : "<dbname>" }

)

Comment by auto [ 20/Dec/10 ]

Author:

{u'login': u'alerner', u'name': u'Alberto Lerner', u'email': u'alerner@10gen.com'}

Message: SERVER-2253 check outcome of config change
https://github.com/mongodb/mongo/commit/e87ba2fefa55ee9ad63e873837a8d0cfbb0f7dbd

Comment by auto [ 20/Dec/10 ]

Author:

{u'login': u'alerner', u'name': u'Alberto Lerner', u'email': u'alerner@10gen.com'}

Message: SERVER-2253 repro in unit test
https://github.com/mongodb/mongo/commit/885dbae1c651f5d5d26f04c9fd845b8876075d49

Generated at Thu Feb 08 02:59:24 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.