Request Timeout V Network Timeout
See original GitHub issueI’m not sure if this is the best place to bring this up, but I’m having some issues being able to differentiate a network timeout from a request timeout.
Is there a way to set the connection timeout separate from the request timeout?
Basically I want to be able to set different thresholds for when a node is not responding at all (which would result in a ConnectTimeout
to one in which the request is just taking too long to process ReadTimeout
ConnectTimeout: HTTPConnectionPool(host=<host>, port=9200): Max retries exceeded with url: /_bulk (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7f44f2c8f510>, 'Connection to <node> timed out. (connect timeout=10)'))
v
ReadTimeout: HTTPConnectionPool(host=<host> port=9200): Read timed out. (read timeout=10)
I’d like to set connect_timeout = 1 and read_timeout = 20
Issue Analytics
- State:
- Created 6 years ago
- Comments:11 (4 by maintainers)
Top GitHub Comments
Great. Thanks for your time Nick! I’ll implement sniffing and go from there. You’ve been very helpful.
I’m going to close the issue for now.