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

Use larger maxTimeMSForHedgedReads hedging_metrics_server_status.js

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.4.0-rc10, 4.7.0
    • Affects Version/s: None
    • Component/s: Internal Code
    • None
    • Fully Compatible
    • ALL
    • v4.4
    • Sharding 2020-06-15
    • 28

      The test currently uses the maxTimeMSForHedgedReads of 10ms (the default is 150ms). This maxTimeMS is too short and can cause this assertion to fail since the request sent with the maxTimeMS can sometimes fail with maxTimeMSExpired so the numAdvantageouslyHedgedOperations will be 0 instead of 1.

            Assignee:
            cheahuychou.mao@mongodb.com Cheahuychou Mao
            Reporter:
            cheahuychou.mao@mongodb.com Cheahuychou Mao
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: