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

cached connections to secondary are not validated against the global ReplicaSetMonitor before using

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Internal Client
    • Labels:
    • Operating System:
      ALL

      Description

      Before creating a new connection to a secondary host, a DBClientReplicaSet connection tries to re-use a previously cached connection to a secondary host. This connection may still exist, though the host may have been detected as inactive earlier by the ReplicaSetMonitor. In this case, we may want to select another secondary host instead of reusing the potentially bad connection.

      see DBCRS::checkLastHost().

        Attachments

          Activity

            People

            Assignee:
            backlog-server-sharding Backlog - Sharding Team
            Reporter:
            greg_10gen Greg Studer
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: