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

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.2.10
    • Component/s: Storage
    • Labels:
      None
    • Fully Compatible
    • ALL
    • 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
    • Storage 2016-11-21
    • 0

      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

        1. repro.patch
          4 kB

            Assignee:
            sulabh.mahajan@mongodb.com Sulabh Mahajan
            Reporter:
            charlie.swanson@mongodb.com Charlie Swanson
            Votes:
            0 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: