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

Throw MaxTimeMSExpired instead of FailedToSatisfyReadPreference when RSM deadline is less than max

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.4.1, 4.7.0
    • Affects Version/s: None
    • Component/s: None
    • Fully Compatible
    • ALL
    • v4.4
    • Sharding 2020-07-13, Sharding 2020-06-29
    • 16

      In server_status_with_timeout_cursors.js, maxTimeMS is set small enough so that it's likely the cursor will time out over its lifetime. It executes find() operations that are expected to fail due to maxTimeMS timeout.

      We should change RemoteCommandTargeterRs so that it throws MaxTimeMsExpired rather than FailedToSatisfyReadPreference if the remaining maxTimeMs is less than the RSM deadline to find a host to expose a more accurate error to the user.

            Assignee:
            janna.golden@mongodb.com Janna Golden
            Reporter:
            haley.connelly@mongodb.com Haley Connelly
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: