Uploaded image for project: 'Ruby Driver'
  1. Ruby Driver
  2. RUBY-1294

Associate SessionPool with Cluster instead of Client

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Minor - P4 Minor - P4
    • 2.5.1
    • Affects Version/s: 2.5.0
    • Component/s: None
    • Labels:
      None

      A SessionPool should be associated with a Cluster, not a Client. This way, new Clients created from existing ones using #with whose options do not require a new Cluster don't create their own pools.
      There is no reason for Clients with the same Clusters to have different SessionPools.

      Note: This is necessary for Mongoid's use of sessions. Different models sometimes have different clients that have the same cluster, no reason to have different session pools for these models.

            Assignee:
            emily.stolfo Emily Stolfo
            Reporter:
            emily.stolfo Emily Stolfo
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: