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

Move per-shard connection management to Shard

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • 3.1.5
    • None
    • Networking, Sharding
    • None
    • Fully Compatible
    • Sharding 3 05/15/15, Sharding 4 06/05/15, Sharding 5 06/26/16

    Description

      With the RemoteCommandTargeter being under Shard, it is prudent to also move the connection pooling to be per-shard as well.

      This also means that different entities within mongos should not cache references to Shard, but use identifiers and look up shards from the shard registry.

      Attachments

        Activity

          People

            kaloian.manassiev@mongodb.com Kaloian Manassiev
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: