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

Use larger maxTimeMSForHedgedReads hedging_metrics_server_status.js

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.4.0-rc10, 4.7.0
    • Component/s: Internal Code
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.4
    • Sprint:
      Sharding 2020-06-15
    • Linked BF Score:
      28

      Description

      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.

        Attachments

          Activity

            People

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

              Dates

              Created:
              Updated:
              Resolved: