[SERVER-18164] "show databases" may show non-existent databases on secondary nodes Created: 22/Apr/15 Updated: 27/Apr/15 Resolved: 22/Apr/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code, Storage |
| Affects Version/s: | 2.6.7 |
| Fix Version/s: | 3.0.0 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | nitzan dana | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operational |
||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Participants: |
| Description |
|
When using a database that doesn't exist on a secondary node, and performing a find query - the database is created on the secondary only. The commands for reproduce: ) Mongo version 2.6.7 |
| Comments |
| Comment by Kaloian Manassiev [ 27/Apr/15 ] |
|
This is correct. If the service instance is restarted, these databases will go away. Just to reiterate, this bug has been fixed in the 3.0 series. |
| Comment by nitzan dana [ 26/Apr/15 ] |
|
In this case, if I reset the mongod service on this secondary machine, will this db vanish? Thanks! |
| Comment by Kaloian Manassiev [ 22/Apr/15 ] |
|
To clarify: This has been fixed in 3.0 where we no longer create in-memory entries on each database access. |