Skip to content

[question] HystrixGatewayFilterFactory retry #551

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

Closed
p555iii opened this issue Sep 17, 2018 · 13 comments
Closed

[question] HystrixGatewayFilterFactory retry #551

p555iii opened this issue Sep 17, 2018 · 13 comments
Labels

Comments

@p555iii
Copy link

p555iii commented Sep 17, 2018

Question
HystrixGatewayFilterFactory with RetryGatewayFilterFactory Is it possible to retry the service on the basis of Hystrix, or how to retry the service on the gateway?

@p555iii p555iii changed the title HystrixGatewayFilterFactory retry [question] HystrixGatewayFilterFactory retry Sep 17, 2018
@ryanjbaxter
Copy link
Contributor

Do you want to retry a request when Hystrix times out?

@p555iii
Copy link
Author

p555iii commented Sep 18, 2018

emmmmmm.....yes

@spencergibb
Copy link
Member

Generally, we recommend retry within the circuit rather than outside.

@p555iii
Copy link
Author

p555iii commented Sep 18, 2018

Spring cloud gateway Is it possible to configure the Ribbon to retry, and if so, what should I do?

@spencergibb
Copy link
Member

@p555iii
Copy link
Author

p555iii commented Sep 18, 2018

Thank you for your busy schedule to reply to me, because we did not find a timeout setting in the RetryGatewayFilterFactory provided by spring cloud gateway, we did not use it.

@spencergibb
Copy link
Member

Retry does not have a timeout associated with it.

@An0nymous0
Copy link

An0nymous0 commented Dec 20, 2018

@spencergibb How to implement retry before triggering hystrix?

com.netflix.hystrix.exception.HystrixRuntimeException: fallbackcmd failed and fallback disabled.

Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /172.16.0.1:7103

Caused by: java.net.ConnectException: Connection refused

@ryanjbaxter
Copy link
Contributor

Using the retry filter

Generally, we recommend retry within the circuit rather than outside.

@An0nymous0
Copy link

image
Hystrix configuration will cause retry to fail

@spencergibb
Copy link
Member

Put hystrix before retry

Sorry, something went wrong.

@An0nymous0
Copy link

Thank you, I didn't think about the reason for the loading order.

Sorry, something went wrong.

@spencergibb
Copy link
Member

Closing as answered

Sorry, something went wrong.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants