Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Done
Priority: Major - P3
Fix Version/s: None
Affects Version/s: 3.1.2
Component/s: Sharding
Labels:
None
Environment:
Sharded cluster, two shards, both standalone servers, 3 config servers, two mongos.

Operating System:
ALL
Steps To Reproduce:
Hide

In the shell:

mongos> use JavaDriverTest switched to db JavaDriverTest mongos> db.test.insert({}) WriteResult({ "nInserted" : 1 }) mongos> db.dropDatabase() { "dropped" : "JavaDriverTest", "ok" : 1 } mongos> db.adminCommand("listDatabases") { "databases" : [ { "name" : "JavaDriverTest", "sizeOnDisk" : 570163200, "empty" : false, "shards" : { "sh01" : 570163200 } }, ...
Show
In the shell: mongos> use JavaDriverTest switched to db JavaDriverTest mongos> db.test.insert({}) WriteResult({ "nInserted" : 1 }) mongos> db.dropDatabase() { "dropped" : "JavaDriverTest", "ok" : 1 } mongos> db.adminCommand("listDatabases") { "databases" : [ { "name" : "JavaDriverTest", "sizeOnDisk" : 570163200, "empty" : false, "shards" : { "sh01" : 570163200 } }, ...
Sprint:
Sharding A (10/09/15)

After dropping a database, it still appears in the response from listDatabases.