[SERVER-18424] listDatabase command includes a database that was just dropped Created: 11/May/15 Updated: 21/Sep/15 Resolved: 21/Sep/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.1.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jeffrey Yemin | Assignee: | Kaloian Manassiev |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Sharded cluster, two shards, both standalone servers, 3 config servers, two mongos. |
||
| Attachments: |
|
||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||
| Steps To Reproduce: | In the shell:
|
||||||||||||||||||
| Sprint: | Sharding A (10/09/15) | ||||||||||||||||||
| Participants: |
| Description |
|
After dropping a database, it still appears in the response from listDatabases. |
| Comments |
| Comment by Kaloian Manassiev [ 21/Sep/15 ] | ||||||||
|
jeff.yemin, our suspicion is that at the time, this bug was temporarily introduced by the catalog management refactoring we did early in the 3.2 development. We are unable to reproduce it anymore and suspect it must have been fixed later on. I am resolving it now. If you end up hitting it again, please open a new bug. | ||||||||
| Comment by Andy Schwerin [ 20/Aug/15 ] | ||||||||
|
jeff.yemin, do you have time to try to reproduce this on 3.1.7 once it's released? | ||||||||
| Comment by Kaloian Manassiev [ 01/Jul/15 ] | ||||||||
|
Sorry for the delayed reply. We are still making changes to the metadata management and I would like to look at this when these changes have been settled. In particular, we are planning of pulling out the chunk/shard operations outside of the metadata classes that represent these sharding concepts. This should take care of some concurrency bugs that are in there currently. | ||||||||
| Comment by Jeffrey Yemin [ 12/May/15 ] | ||||||||
|
I've been able to reproduce this against 3.0.1. Attached is the mongos log file. I can attach additional logs if necessary. This is the snippet for a dropDatabase for which the database was still included in a subsequent listDatabases response:
|