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.
23.98k
stars
4.7k
forks
source link
Hystrix Circuit is closed though the number of failed requests have crossed the error volume threshold #1995
I have a situation where I am listening to certain events from RabbitMQ, collapsing these event messages into batches through hystrix collapser, and creating a hystrix command (with different data) which encapsulates a REST call to an external service. I have enabled the circuit breaker inside command with ERROR_VOLUME_THRESHOLD = 1. Here is the behavior of my application when the external service is down:-
HystrixCommand-1 to HystrixCommand-9 calls Run and then goes to Fallback upon exception
After that HystrixCommand-10 calls run and fallback 10 times, after that circuit getsopen.
Is the Circuit Breaker not shared by the different hystrix command objects, if not then how can we do so, such that after HystrixCommand-1 goes to fallback after the run and circuit get open and HystrixCommand-2 goes directly to fallback.
I have a situation where I am listening to certain events from RabbitMQ, collapsing these event messages into batches through hystrix collapser, and creating a hystrix command (with different data) which encapsulates a REST call to an external service. I have enabled the circuit breaker inside command with ERROR_VOLUME_THRESHOLD = 1. Here is the behavior of my application when the external service is down:- HystrixCommand-1 to HystrixCommand-9 calls Run and then goes to Fallback upon exception After that HystrixCommand-10 calls run and fallback 10 times, after that circuit getsopen. Is the Circuit Breaker not shared by the different hystrix command objects, if not then how can we do so, such that after HystrixCommand-1 goes to fallback after the run and circuit get open and HystrixCommand-2 goes directly to fallback.