[SERVER-5126] db.dropDatabase() fails in sharded environment Created: 28/Feb/12  Updated: 15/Aug/12  Resolved: 30/Apr/12

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Tomas Pecholt Assignee: Randolph Tan
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

sharding with 5 servers running Win2003
config server and mongos run on separate machine with Win2008


Attachments: Text File mongo-session.txt    
Issue Links:
Depends
depends on SERVER-5521 Better user feedback when drop comman... Closed
Operating System: Windows
Participants:

 Description   

calling db.dropDatabase() from mongo shell fails with error.

It seems database was droped from the first shard (deeras36) but other 4 shards still keep their parts.

Repeated call reports success but db is still not droped properly.

Mongo shell session with db.printShardingStatus() attached



 Comments   
Comment by Randolph Tan [ 30/Apr/12 ]

Issue will be tackled on SERVER-5521

Comment by Eliot Horowitz (Inactive) [ 29/Feb/12 ]

Was deeras36:27018 down when you tried the dropDatabase()?

Comment by Tomas Pecholt [ 28/Feb/12 ]

printShardingStatus output was not attached. I paste it here:

mongos> db.printShardingStatus()
— Sharding Status —
sharding version:

{ "_id" : 1, "version" : 3 }

shards:

{ "_id" : "shard0000", "host" : "deeras44:27018" } { "_id" : "shard0001", "host" : "deeras36:27018" } { "_id" : "shard0002", "host" : "deeras37:27018" } { "_id" : "shard0003", "host" : "deeras38:27018" } { "_id" : "shard0004", "host" : "deeras39:27018" }

databases:

{ "_id" : "admin", "partitioned" : false, "primary" : "config" }

mongos>

Generated at Thu Feb 08 03:07:58 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.