[SERVER-26416] Cannot read own write after drop with read/write concern "majority" with inMemory storage engine Created: 30/Sep/16 Updated: 05/Apr/17 Resolved: 01/Nov/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | 3.2.10 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | Sulabh Mahajan |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Steps To Reproduce: | Apply the attached repro.patch, then run the following (on the 3.2 branch + with enterprise modules so that inMemory works):
|
||||||||||||||||
| Sprint: | Storage 2016-11-21 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 0 | ||||||||||||||||
| Description |
|
Under certain circumstances, a client can do the following:
|
| Comments |
| Comment by Sulabh Mahajan [ 01/Nov/16 ] |
|
Duplicate of |
| Comment by Eric Milkie [ 31/Oct/16 ] |
|
Waiting for backport of |