[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: File repro.patch    
Issue Links:
Depends
depends on SERVER-22534 Change ephemeral storage to update du... Closed
depends on SERVER-22533 Enable ReadConcern.Majority tests wit... Closed
Related
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):

python buildscripts/resmoke.py --executor=concurrency_replication --storageEngine=inMemory jstests/concurrency/fsm_all_replication.js

Sprint: Storage 2016-11-21
Participants:
Linked BF Score: 0

 Description   

Under certain circumstances, a client can do the following:

  1. drop a collection
  2. insert a document with write concern "majority"
  3. issue a query and fail to read the document


 Comments   
Comment by Sulabh Mahajan [ 01/Nov/16 ]

Duplicate of SERVER-22533.

Comment by Eric Milkie [ 31/Oct/16 ]

Waiting for backport of SERVER-22533

Generated at Thu Feb 08 04:12:04 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.