Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Missing values in calculation of Zuul Hystrix Timeouts
See original GitHub issueAfter reading the merged PR #2633 I have some questions.
1/ Is it normal to not multiply Ribbon connect and read timeouts by MaxAutoRetries and MaxAutoRetriesNextServer (if they are set in configuration file) ?
Or maybe the hystrix.command.default.execution.isolation.thread.timeoutInMilliseconds is for each request, independently of the number of retries ?
2/ For specific commandKey (service ?), if we have specific Ribbon connect and read timeouts, I think we are ignoring them and setting the default Ribbon properties instead.
Exemple :
I have a service named sample-client and the given configuration :
No hystrix.command.sample-client.execution.isolation.thread.timeoutInMilliseconds
sample-client.ribbon.ReadTimeout=3000
sample-client.ribbon.ConnectTimeout=3000
ribbon.ReadTimeout=2000
ribbon.ConnectTimeout=2000
By default, the hystrix timeout for ma sample-client will be 6000ms and not 4000ms ?
Issue Analytics
- State:
- Created 6 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@rphlmr Thank you very much for the diagram, I think he will help everyone who wants to know about this issue. Although it is 1 am Beijing time, but I did not drowse, I think I will fix this issue. Thanks again ：)
@rphlmr Yes, you’re right. I forgot to say, but in the code I’ve followed the right way