[SERVER-2859] dropping a database may not be replicated properly Created: 29/Mar/11 Updated: 29/Aug/11 Resolved: 29/Mar/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Aaron Staple | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
If we attempt to reclone a missing database after replaying a drop command, we will create an empty database rather than not creating the database at all. |
| Comments |
| Comment by Aaron Staple [ 29/Mar/11 ] |
|
Never mind - it looks like these are in memory only databases created by reads (not on disk databases created by writes). |