[SERVER-43342] createCollection can run concurrently with two phase dropDatabase Created: 16/Sep/19 Updated: 27/Oct/23 Resolved: 25/Sep/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Daniel Gottlieb (Inactive) | Assignee: | Daniel Gottlieb (Inactive) |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Sprint: | Execution Team 2019-10-07 |
| Participants: |
| Description |
|
Two phase dropDatabase releases locks while waiting for collection drops to majority replicate before replicating a drop database oplog entry. A flag is set such that operations which should not run inbetween have a means to do so. Due to how secondaries process a dropDatabase oplog entry, collections created inside this window can result in losing majority committed writes. |
| Comments |
| Comment by Daniel Gottlieb (Inactive) [ 25/Sep/19 ] |
|
I had misdiagnosed a test failure into two separate bugs when there was only one. createCollection/View was correctly being aborted on a drop-pending database. The only bug was |