[SERVER-2107] unable to drop old db using dropDatabase() Created: 16/Nov/10  Updated: 29/Aug/11  Resolved: 29/Aug/11

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

Type: Bug Priority: Major - P3
Reporter: Joseph Wang Assignee: Kristina Chodorow (Inactive)
Resolution: Duplicate Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

> show dbs
admin
local
lp
mortage
mortgage
mortgagecache
purchase
refinance
refinancecash
refinancecashe
> use mortage
switched to db mortage
> db.dropDatabase()

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

> use admin
switched to db admin
> show dbs
admin
local
lp
mortage
mortgage
mortgagecache
purchase
refinance
refinancecash
refinancecashe



 Comments   
Comment by Eliot Horowitz (Inactive) [ 29/Aug/11 ]

See SERVER-2329

Comment by Bernie Hackett [ 02/Jun/11 ]

> actually, we are using master-slave setting – 1 master and 2 slaves. The operation is done on the master.

It looks like SERVER-2859 and SERVER-2329 are this same issue. Compare the log output in SERVER-2329 to Aaron's description in SERVER-2859. I'll leave it up to you to decide about dupes.

Comment by Kristina Chodorow (Inactive) [ 23/Nov/10 ]

Okay, leave a comment if you can and I'll reopen.

Comment by Joseph Wang [ 23/Nov/10 ]

Yes, saw this problem with replica set - 1 primary, 1 secondary, & 1 arbiter.
This was on EC2 linux.

Unfortunately, we deallocated EC2 instance few days ago. Will send the logs if I can reproduce it on staging environment.

Comment by Kristina Chodorow (Inactive) [ 23/Nov/10 ]

So this is with a replica set?

I'm having trouble reproducing this. Could you try a couple of things?

Can you drop other dbs? Can you try:

> use x
> db.runCommand(

{create:"y"}

)
> db.dropDatabase()
> show dbs

and see if x is still listed?

Can you run:

> use admin
> db.runCommand(

{getCmdLineOpts : 1}

)

and send the output?

What OS are you on? Has your db crashed or had an unclean shutdown?

Comment by Joseph Wang [ 23/Nov/10 ]

We didn't see anything in the log.

Note that this problem only shows up in replica set.

Comment by Kristina Chodorow (Inactive) [ 23/Nov/10 ]

Is there anything in the mongod log?

Comment by Joseph Wang [ 16/Nov/10 ]

actually, we are using master-slave setting – 1 master and 2 slaves. The operation is done on the master.

Comment by Joseph Wang [ 16/Nov/10 ]

in replication set setting. Using 1.6.3. Did the operation on the master.

Generated at Thu Feb 08 02:59:00 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.