From 8769e6af89f1d93e688c97a4597d8e2043fe7df5 Mon Sep 17 00:00:00 2001 From: Nora Reidy Date: Fri, 2 Aug 2024 10:31:42 -0400 Subject: [PATCH] DOCSP-40094: Clarify MongoClient.close() behavior (#898) * DOCSP-40094: Clarify MongoClient.close() behavior * RR feedback * RR feedback 2 (cherry picked from commit b9bccea5ad53432032890b55bdba9b249d6859a0) --- source/faq.txt | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/source/faq.txt b/source/faq.txt index 03affac7..9a627c06 100644 --- a/source/faq.txt +++ b/source/faq.txt @@ -102,9 +102,11 @@ during a load spike than it is to complete every operation. When ``MongoClient.close()`` is called by any request, the driver closes all idle sockets and closes all sockets that are in use as they are returned to the pool. Calling ``MongoClient.close()`` -closes only inactive sockets, so you cannot interrupt or terminate -any ongoing operations by using this method. The driver closes these -sockets only when the process completes. +closes only inactive sockets and does not directly terminate +any ongoing operations. The driver closes any in-use sockets only when +the associated operations complete. However, the ``MongoClient.close()`` +method does close existing sessions and transactions, which might indirectly +affect the behavior of ongoing operations and open cursors. What Is the Difference Between "connectTimeoutMS", "socketTimeoutMS" and "maxTimeMS"? -------------------------------------------------------------------------------------