Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-26416

Cannot read own write after drop with read/write concern "majority" with inMemory storage engine

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Duplicate
    • Affects Version/s: 3.2.10
    • Fix Version/s: None
    • Component/s: Storage
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Steps To Reproduce:
      Hide

      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
      

      Show
      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
    • 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

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                11 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: