-
Notifications
You must be signed in to change notification settings - Fork 214
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HystrixTimeout vs HTTPTimeout #101
Comments
It seems heimdall/hystrix/hystrix_client.go Lines 54 to 69 in e5b7967
Lines 21 to 26 in e5b7967
|
I feel there should be 2 different timeouts as within hystrix method there might be other commands also getting executed like http connection setup (if connection is not reused) etc. |
client.Timeout is not being passed on to hystrix setup. Ref: https://github.com/gojek/heimdall/blob/master/hystrix/hystrix_client.go#L80 It seems like a duplicate of the httpClient option. Ref: https://github.com/gojek/heimdall/blob/master/httpclient/client.go#L46 Is it safe to remove |
What is the reason to have two timeouts: HystrixTimeout and HTTPTimeout for
hystrix.Client
? It seems that two points are valid for current implementation:timeout
field inhystrix.Client
is set but never used (maybe bug ?)HTTPTimeout < HystrixTimeout
, thenHystrixTimeout
is never used. And ifHystrixTimeout < HTTPTimeout
then hystrix will return error but goroutine withhttpclient.Do
will be still in blocking state waiting for response or http timeout (problem in hystrix code).The text was updated successfully, but these errors were encountered: