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

secondary_reads_timestamp_visibility.js must wait for operations to be applied on secondary

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.1.7
    • None
    • Replication
    • None
    • Fully Compatible
    • ALL
    • Repl 2019-01-14
    • 20

    Description

      In secondary_reads_timestamp_visibility.js, we wait for the secondary's readConcernMajorityOpTime to advance, then read from the secondary. However, when majority read concern is disabled, the readConcernMajorityOpTime is set based on the node's knowledge of the majority commit point and does not imply that the node has applied through that point. This causes us to read from the secondary before it has applied the operations. We must also wait for the secondary to apply the operations.

      Attachments

        Activity

          People

            tess.avitabile@mongodb.com Tess Avitabile (Inactive)
            tess.avitabile@mongodb.com Tess Avitabile (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: