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

ReplicaSetMonitor::getHostsOrRefresh does not respect wait time in socket connect

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Works as Designed
    • Affects Version/s: 4.0.19
    • Fix Version/s: None
    • Component/s: Networking, Sharding
    • Labels:
      None
    • Operating System:
      ALL

      Description

      This socket timeout is a constant of 5 seconds. It should instead respect the maxWait parameter on getHostOrRefresh when the call to refreshUntilMatches is made. Otherwise this could lead to not respecting a user's MaxTimeMS if the MaxTimeMS is less than 5 seconds.

        Attachments

          Activity

            People

            Assignee:
            backlog-server-servicearch Backlog - Service Architecture
            Reporter:
            matthew.saltz Matthew Saltz
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: