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

Make replication_recovery_test handle doc-level locking storage engine

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.7.0
    • Component/s: None
    • Labels:
      None

      Description

      Multiple tests in replication_recovery_test.cpp check for which order the oplog applier applies them. When using a storage engine that does not support document-level locking the ordering is guaranteed because all jobs get scheduled on the same replication writer thread because the '_id' field is not used when dispatching the jobs. See this code:

      https://github.com/mongodb/mongo/blob/a8af69397f70903f07b3433c03bfc8b1ab92399f/src/mongo/db/repl/oplog_applier_impl.cpp#L190-L201

      We should fix these tests so they don't assume this order.

        Attachments

          Activity

            People

            Assignee:
            henrik.edin Henrik Edin
            Reporter:
            henrik.edin Henrik Edin
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: