Priority: Major - P3
Affects Version/s: None
Fix Version/s: None
When reviewing the behaviour of a NodeJs application compared to a similar Ruby application, the number of connections opened by the drivers do not match.
The following example (using the 3.2.4 node driver) opens 11 connections to each replica set member (10 + 1 monitoring):
A similar program written in Ruby (using the 2.8.0 driver) only opens 2 connections to the PRIMARY and 1 to each SECONDARY:
This doesn't seem to follow the specification:
If minPoolSize is set, the pool MUST immediately create enough connections such that totalConnections >= minPoolSize.
The driver appears to have a method in place to populate the min size of connections but this is only used by the spec runner; not the driver itself.
- Tested with both :min_pool_size and :min_size
- Connection "watching" was done via the following script: