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

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.5.6
    • Component/s: None
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Linked BF Score:
      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

            Assignee:
            jack.mulrow Jack Mulrow
            Reporter:
            jack.mulrow Jack Mulrow
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: