Hystrix is a latency and fault tolerance library designed to isolate points of access to remote systems, services and 3rd party libraries, stop cascading failure and enable resilience in complex distributed systems where failure is inevitable.
24.15k
stars
4.71k
forks
source link
HystrixBadRequestException trigger sleepWindow again afterSleepWindow time over in OPEN circuit. #2005
When circuit is in OPEN state, and after sleepWindow time over, the first request execute and if it give 400 or any HystrixBadRequestException, the state remain the same i.e OPEN. and it trigger the sleepWindow again. which cause agin to be in fallback and this add on the sleepWindow again and again.
Is this behaviour correct ? Since 400 means the client server is up , and it serve the calls, while it give 400, didn’t we close the circuit.
When circuit is in OPEN state, and after sleepWindow time over, the first request execute and if it give 400 or any HystrixBadRequestException, the state remain the same i.e OPEN. and it trigger the sleepWindow again. which cause agin to be in fallback and this add on the sleepWindow again and again.
Is this behaviour correct ? Since 400 means the client server is up , and it serve the calls, while it give 400, didn’t we close the circuit.