Make hedging_metrics_server_status.js determinstic

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.4.0-rc0, 4.7.0
    • Affects Version/s: None
    • Component/s: Internal Code
    • None
    • Fully Compatible
    • ALL
    • v4.4
    • Sharding 2020-03-23
    • 39
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Make the following changes to make hedging_metrics_server_status.js more robust and testing hedge reads easier.

      • Use assert.soon in checkServerStatusHedgingMetrics instead of assert.eq since the the other host might not have responded to the command request when the command finishes.
      • Add a failpoint to SeverSelector that forces the replica set monitor to return all eligible hosts (ignore isMaster latency).
      • Add a failpoint to NetworkInterfaceTL that forces startCommand to target the eligible hosts in alphabetical order (hedging_metrics_server_status.js assumes that it always target the primary first which is not always true).

            Assignee:
            Cheahuychou Mao
            Reporter:
            Cheahuychou Mao
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: