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

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.0.0-rc0
    • Affects Version/s: 3.7.9
    • Component/s: Storage
    • None
    • Fully Compatible
    • ALL
    • Storage NYC 2018-05-21
    • 0

      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.

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

              Created:
              Updated:
              Resolved: