[DOCS-11370] Confused by official mongodb documentation, what is socketTimeoutMS? Created: 28/Feb/18  Updated: 08/Jan/24  Resolved: 31/Oct/22

Status: Closed
Project: Documentation
Component/s: dochub, Server
Affects Version/s: v3.0
Fix Version/s: Server_Docs_20231030

Type: Bug Priority: Minor - P4
Reporter: Anatoly Tarnavsky Assignee: Emet Ozar
Resolution: Won't Fix Votes: 0
Labels: documentation
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 1 year, 14 weeks, 2 days ago
Epic Link: DOCSP-1769

 Description   

I found two different places with different explanation what does:

socketTimeoutMS

do.

Here is written one explanation:

The time in milliseconds to attempt a send or receive on a socket before the attempt times out. The default is never to timeout, though different drivers might vary. See the driver documentation.

But here is given completely different explanation:

The socketTimeoutMS sets the number of milliseconds a socket stays inactive after the driver has successfully connected before closing. If the value is set to 360000 milliseconds, the socket closes if there is no activity during a 30 seconds window.

What does really

socketTimeoutMS

do?



 Comments   
Comment by Education Bot [ 31/Oct/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

Comment by Kay Kim (Inactive) [ 28/Feb/18 ]

Hi Anatoly –
thanks for flagging this. I believe the first definition is correct, but will follow up with the Node driver team to clarify.

Regards

Generated at Thu Feb 08 08:02:40 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.