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

Make DBClientReplicaSet draw connections from a pool

    XMLWordPrintableJSON

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Duplicate
    • 2.3.1
    • None
    • Internal Client

    Description

      DBClientReplicaSet currently manages it's own connections to the replica set members. And because of this, the connections used by each DBClientRS are visible, making it hard for other objects to reuse the same connections when they are idle, and makes it hard for mongos to take account of all the outgoing connections. This setup also causes the DBClientRS to create and destroy more connections more than it should if it were using a connection pool.

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. SERVER-9788 mongos does not re-evaluate read preference once a valid replica set member is chosen

          • Major - P3 - Major loss of function.
          • Closed
          is depended on by

          Question - SERVER-9984 MongoS spawns new connections to secondaries after each change of readPreference tags

          • Major - P3 - Major loss of function.
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-4706 when a socket between mongos and mongod fails, close all connections immediately

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              Unassigned Unassigned
              randolph@mongodb.com Randolph Tan
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: