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

oplog_test should protect access to logOp() with a mutex when using the ephemeralForTest storage engine

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.6.0-rc0
    • Replication
    • None
    • Fully Compatible
    • ALL
    • Repl 2017-09-11, Repl 2017-10-02
    • 0

    Description

      The intent of the test, introduced in SERVER-30212, is to verify multiple uncommitted WriteUnitOfWork that have oplog optimes assigned by repl::logOp() and not to stress the ephemeralForTest storage engine's support for concurrent document insert operations on the oplog collection. By synchronizing access to repl::logOp() with the mutex that's already present in the tests, we can still preserve the existing test cases in oplog_test.cpp which illustrate how logOp() works with storage engines that support document level concurrency.

      Attachments

        Issue Links

          Activity

            People

              benety.goh@mongodb.com Benety Goh
              benety.goh@mongodb.com Benety Goh
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: