[SERVER-2817] (DropDatabase + Sharding + Prefixed DB Name) = drops multiple collections Created: 22/Mar/11  Updated: 29/Feb/12  Resolved: 29/Aug/11

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

Type: Bug Priority: Critical - P2
Reporter: Gaetan Voyer-Perrault Assignee: Unassigned
Resolution: Duplicate Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Ubuntu 10.10


Attachments: File test_sharded_drop.js    
Issue Links:
Duplicate
duplicates SERVER-3471 Drop database caused collections in o... Closed
Operating System: ALL
Participants:

 Description   

See attached or Gist for script to reproduce. Run against an empty sharded test environment as it is dropping data unexpectedly.
https://gist.github.com/882010

------
Original report: http://groups.google.com/group/mongodb-user/browse_thread/thread/f3c0aee26fca75e9#
------

The basic premise is simple, we have three databases with a "prefixed" name.
db2 = db.getSisterDB('fred_sharded') // sharded
db3 = db.getSisterDB('fred_sharded2') // also sharded
db4 = db.getSisterDB('fred_shardednot') // not sharded

If I drop db2, data from db3 also loses data:
db2.runCommand(

{dropDatabase:1}

)

db4 (unsharded) seems unaffected



 Comments   
Comment by Greg Studer [ 29/Aug/11 ]

dup of SERVER-3471

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