Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-13208

Document driver connection pooling logic

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Open
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: drivers, manual

      Description

      Description

      Users are often confused how connection pooling in our drivers works. For example, users are not clear that connection pools are per node not per cluster and will set minPoolSize and maxPoolSize incorrectly. Users are often unaware that there is a separate monitoring connection per node. This makes it difficult for them to reason about how many connections their application will make to their cluster.

      Since we have written the Connection Monitoring and Pooling (CMAP) spec, we should digest it down into a DOCS page similar to how Server Selection Algorithm summarizes our Server Selection spec.

      Scope of changes

      Impact to Other Docs

      MVP (Work and Date)

      Resources (Scope or Design Docs, Invision, etc.)

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              james.kovacs James Kovacs
              Participants:
              Last commenter:
              Nuno Costa Nuno Costa
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Days since reply:
                1 year, 37 weeks, 2 days ago