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.

Sign up for GitHub

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 5 commits into from
Jul 18, 2025
Merged

DOCSP-51630 Add admonition for minPoolSize behavior #1190

Changes from 3 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
93a3501
add callout for minpoolsize
stephmarie17 Jul 17, 2025
9bff7fc
vale edit
stephmarie17 Jul 17, 2025
881d4d1
specify driver version
stephmarie17 Jul 17, 2025
69aea2e
nr feedback
stephmarie17 Jul 18, 2025
bc73989
tech feedback
stephmarie17 Jul 18, 2025
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
View file
Open in desktop
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 of the {+driver-short+} earlier than 6.18.0, idle connections
were not cleaned up when ``minPoolSize`` was set to ``0``. Starting in
version 6.18.0, the connection pool correctly cleans up idle connections
regardless of the ``minPoolSize`` setting.

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

maxIdleTimeMS
Expand Down
Loading