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