Define a reasonable maxTimeMsOverride for the checkOID requests

XMLWordPrintableJSON

    • Fully Compatible
    • ALL
    • v4.4, v4.2, v4.0
    • Sharding 2021-02-08
    • 9
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The requests that we send from the Balancer thread from the primary node of the CSRS doen't have a reasonable time out: the opCtx of that thread doesn't define the maxTimeMs and, since we do not specify the maxTimeMsOverride it is set to Milliseconds::max().

      The main problem is that if any of these requests cannot be fulfilled we will hang there forever.

      The goal of this ticket is to define a reasonable maxTimeMsOverride for those commands (30s).

              Assignee:
              Alexandre Bique (Inactive)
              Reporter:
              Sergi Mateo Bellido
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: