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

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

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Works as Designed
    • Icon: Major - P3 Major - P3
    • None
    • 4.0.19
    • Networking, Sharding
    • None
    • Service Arch
    • 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

            backlog-server-servicearch Backlog - Service Architecture
            matthew.saltz@mongodb.com Matthew Saltz (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: