[SERVER-10983] Issue dropping database in 2.4.6 release Created: 01/Oct/13  Updated: 13/Jan/14  Resolved: 08/Jan/14

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

Type: Bug Priority: Major - P3
Reporter: Chris Beck Assignee: Amalia Hawkins
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Ubuntu 12.04.3 LTS. Package install from 10gen for mongo 2.4.6


Operating System: Linux
Steps To Reproduce:

It seems to happen almost at random during development.

Participants:

 Description   

Failing to drop databases. This issue has appeared randomly a number of time over the past few weeks while working with 2.4.6.

mongos> db.dropDatabase()
{
	"code" : 16338,
	"ok" : 0,
	"errmsg" : "exception: Dropping collection failed on the following hosts: mongo-cl1-sh5/mongo-cl1-rs5-m1:27101,mongo-cl1-rs5-r1:27102: { ok: 0.0, errmsg: \"ns not found\" }"
}
mongos>

Databases listed...

mongos> show dbs;
admin	(empty)
config	0.109375GB
lld	489.3017578125GB
lld_mrd	56.009765625GB
test	(empty)
 
{  "_id" : "lld_mrd",  "partitioned" : true,  "primary" : "mongo-cl1-sh10" }
		lld_mrd.lld_mrd
			shard key: { "_id" : 1 }
			chunks:
				mongo-cl1-sh5	1
			{ "_id" : { "$minKey" : 1 } } -->> { "_id" : { "$maxKey" : 1 } } on : mongo-cl1-sh5 Timestamp(1, 0) 

I have stopped the balancer, nothing is running.

This is quite a big issue for us.



 Comments   
Comment by Amalia Hawkins [ 08/Jan/14 ]

Chris – since I haven't heard back from you in two months, I'm going to assume this problem is no longer an issue and close the ticket. If this is not the case, please reopen.

Comment by Amalia Hawkins [ 04/Nov/13 ]

Chris, my apologies for the delay in response. In order to help diagnose your issue, could you provide me with the following information?

Top Priority

  • Can you use mongodump (via a mongos) to get a copy of your config database and attach it to this issue?
  • Can you still query the "dropped" databases? (i.e., can you run a findOne() on a collection in lld_mrd.)
    • The reason I ask is because I want to ensure you're not running into SERVER-4804.
  • Are you running with replica sets?
  • Did you make any other changes to your setup (ports, etc.) when you upgraded to 2.4.6?
  • Did you make sure to use config before you stopped the balancer? (Just covering all the bases.)

Second Priority

  • Are you seeing any errors in your log files?
  • Have you tried to log in to the primary for each shard (assuming you're running with replica sets, otherwise just the mongod server for each shard), and dropping the database from each shard?
  • After the balancer has been turned off and the database dropped, have you tried running db.adminCommand("flushRouterConfig") on your mongos's?
Comment by Chris Beck [ 02/Oct/13 ]

mongo-cl1-sh5:PRIMARY> show dbs;
admin	(empty)
config	(empty)
lld	51.9287109375GB
lld_mrd	5.951171875GB
lld_mrd_beta	5.951171875GB
local	22.0673828125GB
mongo-cl1-sh5:PRIMARY> use lld_mrd
switched to db lld_mrd
mongo-cl1-sh5:PRIMARY> show collections;
system.indexes
mongo-cl1-sh5:PRIMARY> 

venatus@ubuntu:~$ mongo
MongoDB shell version: 2.4.6
connecting to: test
mongos> show dbs;
admin	(empty)
config	0.109375GB
lld	523.28515625GB
lld_mrd	56.009765625GB
lld_mrd_beta	61.5107421875GB
test	(empty)
mongos> use lld_mrd
switched to db lld_mrd
mongos> db.dropDatabase()
{
	"code" : 16338,
	"ok" : 0,
	"errmsg" : "exception: Dropping collection failed on the following hosts: mongo-cl1-sh5/mongo-cl1-rs5-m1:27101,mongo-cl1-rs5-r1:27102: { ok: 0.0, errmsg: \"ns not found\" }"
}
mongos> 

Comment by Eliot Horowitz (Inactive) [ 02/Oct/13 ]

Can you login into mongo-cl1-sh5 and do a "show dbs"

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