[SERVER-10783] MongoDB displays databases even after dropDatabase() has completed successfully Created: 16/Sep/13 Updated: 10/Dec/14 Resolved: 19/Mar/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | 2.4.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tito Ciuro | Assignee: | Unassigned |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Mac OS X 10.8/10.9 |
||
| Issue Links: |
|
||||||||||||
| Operating System: | OS X | ||||||||||||
| Steps To Reproduce: | 1) Launch mongo Something really interesting once the shell has opened: TurboMonkey:~ tito$ mongo List all databases again and voilĂ ! They're back! > show dbs |
||||||||||||
| Participants: | |||||||||||||
| Description |
|
I have several databases listed: > show dbs Except for developer and local, I remove them one by one like this: > use befd1bcc5e MongoDB reports something like this: Mon Sep 16 08:14:53.085 [conn7305] dropDatabase befd1bcc5e starting When I display all available databases, they're still reported: > show dbs These UUID-looking databases won't die. |
| Comments |
| Comment by Stennie Steneker (Inactive) [ 19/Mar/14 ] |
|
Hi Tito, Please be advised I'm now closing this issue as we have been unable to reproduce the reported problem. If you do have any further information that would help us reproduce this issue (as per the last questions from Dan), please let us know. Thanks, |
| Comment by Daniel Pasette (Inactive) [ 09/Oct/13 ] |
|
This could this be a side-effect of using MongoHub? Can you try without MongoHub in the reproduction? Querying an empty collection has the effect of caching the database name in the server, even if it's empty. You can see this easily by opening two shells, querying an empty collection with one and then running show dbs with the other. You'll see that the database is listed even though it's empty. |
| Comment by Tito Ciuro [ 01/Oct/13 ] |
|
This is my setting: 1) I have mongo running |
| Comment by Daniel Pasette (Inactive) [ 30/Sep/13 ] |
|
Are you able to provide a precise repro? |
| Comment by Tito Ciuro [ 29/Sep/13 ] |
|
Actually, I spoke too soon. I still see this with 2.4.6. I see a lot of "ghost" databases that go away the minute I restart MongoDB. Is there a way to trigger a "cleanup" of some sort? |
| Comment by Tito Ciuro [ 18/Sep/13 ] |
|
Hello Dan, I have a combination of clients: RoboMongo and MongoHub. These two clients are used to query documents and work in read-only mode. The other client is a Node.js app, which reads and writes data. Please note that the "ghost" databases are created when the unit tests execute and are supposed to be removed on tear down. The configuration is standalone, both client and server running on the same Mac (development phase.) FWIW, upgrading to v2.4.6 has solved the issue. I worked exactly the same way and I cannot reproduce this problem. |
| Comment by Daniel Pasette (Inactive) [ 17/Sep/13 ] |
|
Couple questions.
|