checkStatus in DBClientReplicaSet has no explicit socket timeout

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 2.2.4, 2.4.0-rc2
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • 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.
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      ...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.

            Assignee:
            Unassigned
            Reporter:
            Greg Studer (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: