-
Type: New Feature
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Connections
-
None
-
Minor Change
CMAP spec now requires that drivers begin creating working connections (i.e. handshaken & authed) up to min pool size as soon as the pool is created.
The current driver behavior, as now documented on https://docs.mongodb.com/ruby-driver/master/tutorials/ruby-driver-create-client/#details-on-connection-pooling, is the driver only creates actual network connections to the servers when they are needed by operations. Specifying a min pool size affects how many established connections the driver will keep around, but does not cause the driver to eagerly create that many ready to be used connections.
Once the behavior changes are made, production guidance per https://jira.mongodb.org/browse/RUBY-1712 needs to be updated for the new behavior.
- is duplicated by
-
RUBY-1808 min_pool_size does not behave according to spec
- Closed
- is related to
-
RUBY-1717 Disconnecting connection pool should not reconnect connections
- Closed
-
RUBY-1441 Driver connects to cluster when closing stale sockets
- Closed
-
RUBY-1770 Create connection objects on demand only
- Closed
-
RUBY-1712 Min connection pool size guidance for production deployments
- Closed
- links to