failsafe
failsafe copied to clipboard
failsafe-lib
Fault tolerance and resilience patterns for the JVM
Following #308, add a warmup options for rate limiters.
CircuitBreaker policy should allow jittering so that if there is short interrupt, the circuit breaker will not close at the same time (similar to how RetryPolicy works). It is useful...
Consider adding onAbort event listeners for CircuitBreaker which are called when `CircuitBreakerOpenException` is thrown. Please comment if you're interested in something like this.
Some thoughts around creating a chaos policy: - randomly delay, drop, reorder executions - randomly duplicate executions (dupe request/response) - similar settings that the [atomix chaos controller](https://github.com/atomix/chaos-controller) supports
As part of #208 there was a suggestion to support something like `withFailureThreshold(thresh, minPeriod, period)` for time based circuit breakers. Let's discuss that here. @armelbd would this feature be for...
> Not a Contribution. Currently Failsafe only allows to make a single retry at a time. Sometimes it's beneficial to make several retries at the same time and hope that...
> Not a Contribution. As mentioned in #159 and #291 there is an additional layer on top of hedged/staggered retries that we may need to support: backup requests. In short,...
> Not a Contribution. Currently a lot of internal APIs are well, internal. It should be possible to implement a different `Timeout` or `Retry` policy from an application package. This...
Something has changed after 2.4.2. A combination of `Timeout` and `RetryPolicy` with `getStageAsync()` makes Failsafe to hang sometimes. Here is an example that's reproducible on a `2.4.x`, but not on...
This could place an easy cap on concurrent executions/requests through the circuit. May need to use something like ExecutionRejectedException with max concurrency is reached.
Metadata
Owner
Metadata
Fault tolerance and resilience patterns for the JVM