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

checkStatus in DBClientReplicaSet has no explicit socket timeout

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.2.4, 2.4.0-rc2
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Steps To Reproduce:
      Hide

      Blackhole a connection from mongos to a replica set primary - the monitor hangs.

      Show
      Blackhole a connection from mongos to a replica set primary - the monitor hangs.

      Description

      ...this is bad since we hold a lock which prevents other connection checks until the replSetGetStatus returns. Other timeouts for the ReplicaSetMonitors are aggressively set to 5s, we should probably do this here.

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            greg_10gen Greg Studer
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: