From a98618e8bf9f956428a2606ddee634f976e4f63c Mon Sep 17 00:00:00 2001 From: norareidy Date: Thu, 1 Aug 2024 11:33:59 -0400 Subject: [PATCH 1/3] DOCSP-40094: Clarify MongoClient.close() behavior --- source/faq.txt | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/source/faq.txt b/source/faq.txt index 03affac70..10c40f1fb 100644 --- a/source/faq.txt +++ b/source/faq.txt @@ -106,6 +106,12 @@ 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. +.. note:: + + The ``MongoClient.close()`` method closes 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"? ------------------------------------------------------------------------------------- From c725ff34052eabf7bee0b0583d0a86a9db96cb05 Mon Sep 17 00:00:00 2001 From: norareidy Date: Thu, 1 Aug 2024 16:04:35 -0400 Subject: [PATCH 2/3] RR feedback --- source/faq.txt | 14 +++++--------- 1 file changed, 5 insertions(+), 9 deletions(-) diff --git a/source/faq.txt b/source/faq.txt index 10c40f1fb..b8d46b11f 100644 --- a/source/faq.txt +++ b/source/faq.txt @@ -102,15 +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. - -.. note:: - - The ``MongoClient.close()`` method closes existing sessions and - transactions, which might indirectly affect the behavior of ongoing - operations and open cursors. +closes only inactive sockets and does not actively terminate +any ongoing operations. The driver closes in-use sockets only when +the operation completes. 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"? ------------------------------------------------------------------------------------- From 9717a6c6ab586f70df13d446a5c9ed268aff372d Mon Sep 17 00:00:00 2001 From: norareidy Date: Fri, 2 Aug 2024 10:20:57 -0400 Subject: [PATCH 3/3] RR feedback 2 --- source/faq.txt | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/source/faq.txt b/source/faq.txt index b8d46b11f..9a627c064 100644 --- a/source/faq.txt +++ b/source/faq.txt @@ -102,10 +102,10 @@ 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 and does not actively terminate -any ongoing operations. The driver closes in-use sockets only when -the operation completes. However, the ``MongoClient.close()`` method -does close existing sessions and transactions, which might indirectly +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"?