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
In previous (v1.4) versions of Otoroshi, it was possible to activate circuit breaker at route (service) level.
Now (v16+), it seems to be possible only at a global scope (in Danger Zone).
Working actually on Load Balancing instances of backends, we have noticed that the HealthChecker uses Circuit Breaker to kick instances of backend that are not healthy.
So we figure out that Circuit Breaker is required to implement this "HA" strategy.
We are not yet comfortable with Circuit Breaker, and we are not ready to activate it globally on our Otoroshi.
Is it possible to restore the capability of activating Circuit Breaker at route level, even if circuit breaker is disabled at a global level?
Thanks!
The text was updated successfully, but these errors were encountered:
@cbois We'll talk about it internally next week and we'll get back to you. I'm not in favor of being able to disable circuit breaker in routes as it's intended to be the defaut on purpose. The circuit breaker is default since 2018 in otoroshi with a flag to be able to disable it (because of retro compatibility) and now it's always enabled on purpose
Hi!
In previous (v1.4) versions of Otoroshi, it was possible to activate circuit breaker at route (service) level.
Now (v16+), it seems to be possible only at a global scope (in Danger Zone).
Working actually on Load Balancing instances of backends, we have noticed that the HealthChecker uses Circuit Breaker to kick instances of backend that are not healthy.
So we figure out that Circuit Breaker is required to implement this "HA" strategy.
We are not yet comfortable with Circuit Breaker, and we are not ready to activate it globally on our Otoroshi.
Is it possible to restore the capability of activating Circuit Breaker at route level, even if circuit breaker is disabled at a global level?
Thanks!
The text was updated successfully, but these errors were encountered: