Fix numOperationsRetriedAtLeastOnceDueToOverload logic for zero-budget

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 9.0.0-rc1
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • Fully Compatible
    • ALL
    • ClusterScalability 22Jun-6Jul, ClusterScalability 6Jul-20Jul
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Behavior

      New unit tests added in PR 55031 (SERVER-127628) discovered that when there is zero retry-budget, no retries occur, but sharding statistic numOperationsRetriedAtLeastOnceDueToOverload is still incremented by 1.

      Root Cause

      Currently, numOperationsRetriedAtLeastOnceDueToOverload is incremented whenever a SystemOverloadedError label is seen, even when no retries occurs.

      Based on the name of the variable, this behavior seems incorrect, but logging this ticket to let the WR team take a closer look.

            Assignee:
            Jordan Glassley
            Reporter:
            Jordan Glassley
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: