[SERVER-11080] dropDatabase command failed to drop database from all shards. Created: 08/Oct/13 Updated: 10/Dec/14 Resolved: 19/Mar/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.4.6 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | jitendra | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | sharding | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
OEL linux |
||
| Operating System: | Linux |
| Steps To Reproduce: | Insert 100 GB data to sharding cluster for database_1. |
| Participants: |
| Description |
|
Hi, We have following configuration of mongodb:(journal enabled) We ran dropDatabase command from mongos, got below error: ", dropDatabase dropped the database only from shard1. i again ran dropDatabase command from mongos and get "ok" but database was not deleted from shard2 to shard10. We got below log in mongos: I have following questions: please help me to resolve this issue T&R, |
| Comments |
| Comment by Stennie Steneker (Inactive) [ 19/Mar/14 ] |
|
Hi JRV, Please be advised I'm closing this issue due to inactivity. I would also note that the SERVER project is intended for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-users group (http://groups.google.com/group/mongodb-user) or ask specific questions on Stack Overflow / ServerFault. Thanks, |
| Comment by Linda Qin [ 28/Oct/13 ] |
|
Hi JRV, Following up with you on this subject since we haven't heard from you in a while. Could you please let us know if you were able to drop the database and do you have any progress to answer the questions in my last comment? Thanks, |
| Comment by Linda Qin [ 17/Oct/13 ] |
|
Hi JRV, Please find my comments inline:
To drop the database in the above condition, you can login to the primary of each shard (if it is a replica set for each shard, otherwise just login the mongod server for each shard), and drop that database from each shard.
This means the configurations of database [00031013] were already removed from the config database when you retrying deleting this database again.
If it is a sharded cluster, you have to use dropDatabase to drop the db from mongos to cleanup the database configurations for db from config database. To help us diagnose why it failed to drop the database from mongos, could you please:
Thanks, |