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

Move per-shard connection management to Shard

XMLWordPrintableJSON

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

      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.

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

              Created:
              Updated:
              Resolved: