You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Could you please confirm if the issue is still open for contributions? I'd like to proceed with further improvements if possible. Can you assign this task to me.
Could you please confirm if the issue is still open for contributions? I'd like to proceed with further improvements if possible. Can you assign this task to me.
If you can help me with this problem. It will be very much appreciated
Could you please confirm if the issue is still open for contributions? I'd like to proceed with further improvements if possible. Can you assign this task to me.
My request is that when the downstream service calls the upstream service and there are 3 consecutive 5xx errors, the service will be kicked out and no longer send requests to the upstream service within 30 seconds. Directly return "upstream service is unavailable". Just like istio.
Now: There are 3 consecutive 5xx errors, and the downstream service will still request the upstream service
hi @ogetysaisandeep work on this would definitely be appreciated
adding sandbox/examples can take quite a few iterations as there are a few moving parts
overall i would say the thing to understand is that while ~all the examples are tested and so function as a kind of integration test, they are "docs-first" - ie the walkthrough/steps that the end user can take from them is the most important part
if you are happy to take this on im happy to work with you and review
I searched for a long time in the examples directory and docs and wanted to test the outlier_detection function.
But it never works, not sure where is wrong with the configuration! I hope you have an outlier_detection example in the examples directory.
The following configuration will not automatically kick the host out regardless of how many 500 errors the upstream http service has.
The text was updated successfully, but these errors were encountered: