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

mirrored_reads.js doesn't wait for all mirrored reads to resolve

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Critical - P2 Critical - P2
    • None
    • Affects Version/s: None
    • Component/s: None
    • Service Arch
    • ALL
    • 126

      When we wait for read mirroring to complete here, we never check that our "sent" value is equal to our "resolved" value. This means that occasionally, we have achieved the desired level of mirroring but there are still operations being mirrored to secondaries. This becomes a problem when we run 0% mirroring tests on slow variants, because even a single late operation breaks the statistical bounds in the test.

            Assignee:
            backlog-server-servicearch [DO NOT USE] Backlog - Service Architecture
            Reporter:
            ben.caimano@mongodb.com Benjamin Caimano (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: