-
Type: Story
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: 1.20.0, 1.21.0, 1.22.0
-
Component/s: Connectivity
-
None
-
3
-
Not Needed
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'.
- related to
-
COMPASS-4052 Queries longer than 60 seconds time out even with MAXTIMEMS set to a value greater than 60 seconds
- Closed