Skip to content

DOCSP-51630 Add admonition for minPoolSize behavior #1190

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions source/connect/connection-options/connection-pools.txt
Original file line number Diff line number Diff line change
Expand Up @@ -165,6 +165,18 @@ object:
minPoolSize: 10
});

.. note::

A ``MongoClient`` configured with ``maxIdleTimeMS`` and ``minPoolSize``
set to ``0`` is optimal for workloads with sustained periods of low activity.
This configuration allows the connection pool to close unused connections
during periods of inactivity.

In versions earlier than 6.18.0, the {+driver-short+} did not close idle
connections when ``minPoolSize`` was set to ``0`` during periods of
inactivity. Starting in version 6.18.0, the connection pool correctly closes
idle connections regardless of the ``minPoolSize`` setting.

.. _node-connection-pool-max-idle-time:

maxIdleTimeMS
Expand Down
Loading