[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:
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
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 – Regards |