Hedged async RPC runner should use dynamic backoff instead of delay

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 6.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • Service Arch 2022-11-14
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The hedged async RPC runner (async_rpc::sendHedgedCommand) is mistakenly using a fixed delay between retry attempts instead of a dynamic one - it only calls getNextRetryDelay once and uses that value for each retry, instead of calculating a new value between each retry attempt. We should fix this and add a test for it. 

            Assignee:
            George Wangensteen (Inactive)
            Reporter:
            George Wangensteen (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: