Hystrix Configuration

Sets the group key to use. The default value is CamelHystrix.

Sets the thread pool key to use. Will by default use the same value as groupKey has been configured to use.

Whether to use a HystrixCircuitBreaker or not. If false no circuit-breaker logic will be used and all requests permitted. <p> This is similar in effect to circuitBreakerForceClosed() except that continues tracking metrics and knowing whether it should be open/closed, this property results in not even instantiating a circuit-breaker.

Error percentage threshold (as whole number such as 50) at which point the circuit breaker will trip open and reject requests. <p> It will stay tripped for the duration defined in circuitBreakerSleepWindowInMilliseconds; <p> The error percentage this is compared against comes from HystrixCommandMetrics.getHealthCounts().

If true the HystrixCircuitBreaker#allowRequest() will always return true to allow requests regardless of the error percentage from HystrixCommandMetrics.getHealthCounts(). <p> The circuitBreakerForceOpen() property takes precedence so if it set to true this property does nothing.

If true the HystrixCircuitBreaker.allowRequest() will always return false, causing the circuit to be open (tripped) and reject all requests. <p> This property takes precedence over circuitBreakerForceClosed();.

Minimum number of requests in the metricsRollingStatisticalWindowInMilliseconds() that must exist before the HystrixCircuitBreaker will trip. <p> If below this number the circuit will not trip regardless of error percentage.

The time in milliseconds after a HystrixCircuitBreaker trips open that it should wait before trying requests again.

Number of concurrent requests permitted to HystrixCommand.run(). Requests beyond the concurrent limit will be rejected. <p> Applicable only when executionIsolationStrategy == SEMAPHORE.

What isolation strategy HystrixCommand.run() will be executed with. <p> If THREAD then it will be executed on a separate thread and concurrent requests limited by the number of threads in the thread-pool. <p> If SEMAPHORE then it will be executed on the calling thread and concurrent requests limited by the semaphore count.

Enum values:

Whether the execution thread should attempt an interrupt (using Future#cancel ) when a thread times out. <p> Applicable only when executionIsolationStrategy() == THREAD.

Time in milliseconds at which point the command will timeout and halt execution. <p> If executionIsolationThreadInterruptOnTimeout == true and the command is thread-isolated, the executing thread will be interrupted. If the command is semaphore-isolated and a HystrixObservableCommand, that command will get unsubscribed.

Whether the timeout mechanism is enabled for this command.

Number of concurrent requests permitted to HystrixCommand.getFallback(). Requests beyond the concurrent limit will fail-fast and not attempt retrieving a fallback.

Whether HystrixCommand.getFallback() should be attempted when failure occurs.

Time in milliseconds to wait between allowing health snapshots to be taken that calculate success and error percentages and affect HystrixCircuitBreaker.isOpen() status. <p> On high-volume circuits the continual calculation of error percentage can become CPU intensive thus this controls how often it is calculated.

Maximum number of values stored in each bucket of the rolling percentile. This is passed into HystrixRollingPercentile inside HystrixCommandMetrics.

Whether percentile metrics should be captured using HystrixRollingPercentile inside HystrixCommandMetrics.

Duration of percentile rolling window in milliseconds. This is passed into HystrixRollingPercentile inside HystrixCommandMetrics.

Number of buckets the rolling percentile window is broken into. This is passed into HystrixRollingPercentile inside HystrixCommandMetrics.

This property sets the duration of the statistical rolling window, in milliseconds. This is how long metrics are kept for the thread pool. The window is divided into buckets and rolls by those increments.

Number of buckets the rolling statistical window is broken into. This is passed into HystrixRollingNumber inside HystrixCommandMetrics.

Whether HystrixCommand execution and events should be logged to HystrixRequestLog.

Core thread-pool size that gets passed to java.util.concurrent.ThreadPoolExecutor#setCorePoolSize(int).

Maximum thread-pool size that gets passed to ThreadPoolExecutor#setMaximumPoolSize(int) . This is the maximum amount of concurrency that can be supported without starting to reject HystrixCommands. Please note that this setting only takes effect if you also set allowMaximumSizeToDivergeFromCoreSize.

Keep-alive time in minutes that gets passed to ThreadPoolExecutor#setKeepAliveTime(long,TimeUnit).

Max queue size that gets passed to BlockingQueue in HystrixConcurrencyStrategy.getBlockingQueue(int) This should only affect the instantiation of a threadpool - it is not eliglible to change a queue size on the fly. For that, use queueSizeRejectionThreshold().

Queue size rejection threshold is an artificial max size at which rejections will occur even if maxQueueSize has not been reached. This is done because the maxQueueSize of a BlockingQueue can not be dynamically changed and we want to support dynamically changing the queue size that affects rejections. <p> This is used by HystrixCommand when queuing a thread for execution.

Duration of statistical rolling window in milliseconds. This is passed into HystrixRollingNumber inside each HystrixThreadPoolMetrics instance.

Number of buckets the rolling statistical window is broken into. This is passed into HystrixRollingNumber inside each HystrixThreadPoolMetrics instance.

Allows the configuration for maximumSize to take effect. That value can then be equal to, or higher, than coreSize.