[SERVER-6751] db.dropDatabase() on a sharded database causes only one shard to be cleared Created: 10/Aug/12  Updated: 15/Aug/12  Resolved: 10/Aug/12

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

Type: Bug Priority: Major - P3
Reporter: Pavel Baranov Assignee: Kevin Matulef
Resolution: Duplicate Votes: 0
Labels: mongos, sharding
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

2.6.18-194.32.1.el5 #1 SMP Wed Jan 5 17:52:25 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
CentOS release 5.5


Issue Links:
Duplicate
duplicates SERVER-5521 Better user feedback when drop comman... Closed
Operating System: Linux
Participants:

 Description   

Single database sharded across two shards.
Connecting to mongos and running: db.dropDatabase() returns
mongos> db.dropDatabase()

{ "dropped" : "peek", "ok" : 1 }

All of the chunks on shard00001 are cleared, however shard00002 still has all the files: peek.0 peek.1 peek.2 etc


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