[DOCS-13208] Document driver connection pooling logic Created: 07/Nov/19  Updated: 30/Oct/23  Resolved: 01/Nov/21

Status: Closed
Project: Documentation
Component/s: drivers, manual
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Task Priority: Major - P3
Reporter: James Kovacs Assignee: Unassigned
Resolution: Won't Do Votes: 1
Labels: docs-administration, quick-win
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
Related
Participants:
Days since reply: 4 years, 13 weeks, 6 days ago
Epic Link: DOCSP-1769

 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.)


Generated at Thu Feb 08 08:07:11 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.