From 9717a6c6ab586f70df13d446a5c9ed268aff372d Mon Sep 17 00:00:00 2001 From: norareidy Date: Fri, 2 Aug 2024 10:20:57 -0400 Subject: [PATCH] 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 b8d46b11..9a627c06 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"?