[COMPASS-4381] Allow to set socketTimeoutMS in the connection form Created: 03/Aug/20  Updated: 23/Mar/22  Resolved: 23/Mar/22

Status: Closed
Project: Compass
Component/s: Connectivity
Affects Version/s: 1.20.0, 1.21.0, 1.22.0
Fix Version/s: 1.31.0

Type: Story Priority: Major - P3
Reporter: Maurizio Casimirri Assignee: Unassigned
Resolution: Done Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screenshot 2022-03-23 at 13.04.36.png    
Issue Links:
Related
related to COMPASS-4052 Queries longer than 60 seconds time o... Closed
Story Points: 3
Documentation Changes: Not Needed

 Description   

There is no way to specify `socketTimeoutMS` as a field in the connection screen, this is necessary to use `socketTimeoutMS` when connecting with ssl certificates.

Context:

`socketTimeoutMS` is the maximum amount of time for a connection in the connection pool to be inactive. After that the socket is closed and a new connection is established.

`socketTimeoutMS` can only be specified as a connection option (in compass as a URI parameter) and affects all the operations. Unfortunately the timeout is triggered even in case of a long query, when the time of first byte is going over the `socketTimeoutMS` threshold.

Since the default `socketTimeoutMS` is 360000 milliseconds, queries / operations taking longer than that to respond expires with an unclear error message: 'connection 33 to xxx.xxx.xxx.xxx:27017 timed out'.


Generated at Wed Feb 07 22:36:10 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.