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

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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.4.1, 4.7.0
    • Component/s: None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.4
    • Sprint:
      Sharding 2020-07-13, Sharding 2020-06-29
    • Linked BF Score:
      16

      Description

      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.

        Attachments

          Activity

            People

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

              Dates

              Created:
              Updated:
              Resolved: