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

Use rst.awaitLastOpCommitted() in secondary_reads_timestamp_visibility.js to correctly wait for the secondary to catch up

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.7.9
    • Fix Version/s: 4.0.0-rc0
    • Component/s: Storage
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Storage NYC 2018-05-21
    • Linked BF Score:
      0

      Description

      The test secondary_reads_timestamp_visibility.js uses awaitReplication to wait for the secondary to catch up to the majority commit point. This can cause failures return incorrect results when doing majority reads on the secondary.

      The test should be modified to use awaitLastOpCommitted instead, which guarantees the secondary has committed the last oplog on the primary.

        Attachments

          Activity

            People

            Assignee:
            louis.williams Louis Williams
            Reporter:
            louis.williams Louis Williams
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: