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
Let's suppose I have a 3rd party @Client protected with @CircuitBreaker(attemps="3", reset="20s") that handles hundreds of successful requests per second.
But for some reason, a single malformed request is sent to the client. That request will result in a 4xx/5xx error code. As the error is due to malformed input, any retry will fail too. When it run out of retries, the circuit becomes open.
All those hundreds of successful requests will be rejected during 20s, resulting in thousands of errors.
This is what I've observed from using @CircuitBreaker. Am I using it wrong? Is it expected that a single failing request (with failing retries) opens a healthy circuit?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Let's suppose I have a 3rd party
@Client
protected with@CircuitBreaker(attemps="3", reset="20s")
that handles hundreds of successful requests per second.But for some reason, a single malformed request is sent to the client. That request will result in a 4xx/5xx error code. As the error is due to malformed input, any retry will fail too. When it run out of retries, the circuit becomes open.
All those hundreds of successful requests will be rejected during
20s
, resulting in thousands of errors.This is what I've observed from using
@CircuitBreaker
. Am I using it wrong? Is it expected that a single failing request (with failing retries) opens a healthy circuit?Beta Was this translation helpful? Give feedback.
All reactions