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

operation_time_read_and_write_concern.js should use awaitLastOpCommitted after re-enabling replication

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.5.6
    • None
    • None
    • Fully Compatible
    • ALL
    • 0

    Description

      operation_time_read_and_write_concern.js disables replication to secondaries using a failpoint, makes a local write to the primary, re-enables replication, then waits for the write to replicate to the secondaries before issuing a read with readConcern majority, expecting the locally written document to be returned. Currently the test uses ReplTest.awaitReplication, which blocks until the secondaries last applied optime matches the primary's, but it should use ReplTest.awaitLastOpCommitted, which blocks until their last committed optime is caught up. This will ensure the majority read returns the expected documents.

      Attachments

        Activity

          People

            jack.mulrow@mongodb.com Jack Mulrow
            jack.mulrow@mongodb.com Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: