-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Major - P3
-
None
-
Affects Version/s: 1.8.2
-
Component/s: None
-
None
-
ALL
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
We have a cluster of three shards, with a number of sharded databases (one per day, because we need to be able to remove old data, and remove just fragments the database, killing performance). However, when I manually drop databases, some stick around and cannot be removed. Just before the output shown below I had removed every database with the "complete" and "fragments" prefixes, but still five of them showed up with show dbs, and when I remove them again they still show up:
> show dbs
admin (empty)
complete_20110821 0.40625GB
complete_20110822 13.9013671875GB
config 0.046875GB
fragments_20110821 0.40625GB
fragments_20110822 27.89453125GB
fragments_20110823 1.90625GB
test (empty)
> db.getSiblingDB("complete_20110821").dropDatabase()
{ "dropped" : "complete_20110821", "ok" : 1 }
> show dbs
admin (empty)
complete_20110821 0.40625GB
complete_20110822 13.9013671875GB
config 0.046875GB
fragments_20110821 0.40625GB
fragments_20110822 27.89453125GB
fragments_20110823 1.90625GB
test (empty)
> db.getSiblingDB("complete_20110822").dropDatabase()
{ "dropped" : "complete_20110822", "ok" : 1 }
> show dbs
admin (empty)
complete_20110821 0.40625GB
complete_20110822 5.951171875GB
config 0.046875GB
fragments_20110821 0.40625GB
fragments_20110822 27.89453125GB
fragments_20110823 1.90625GB
test (empty)
Notice that when I drop "complete_20110822" the size changes (dropping it again does not change the size now, through).
It doesn't matter how many times I run the remove command, these databases still show up.