@HystrixCommandBinding public class HystrixCommandInterceptor extends Object
If SynchronousCircuitBreaker
is used it is not possible to track the execution inside a Hystrix command because a TimeoutException
should be
always counted as a failure, even if the command execution completes normally.
We never use HystrixCommand#queue()
for async execution. Mostly to workaround various problems of Asynchronous
Retry
combination. Instead, we
create a composite command and inside its run() method we execute commands synchronously.
Modifier and Type | Field and Description |
---|---|
static String |
SYNC_CIRCUIT_BREAKER_KEY
This config property key can be used to disable synchronous circuit breaker functionality.
|
Constructor and Description |
---|
HystrixCommandInterceptor(Boolean nonFallBackEnable,
Config config,
<any> fraction,
BeanManager beanManager,
RequestContext requestContext) |
Modifier and Type | Method and Description |
---|---|
Object |
interceptCommand(InvocationContext ic) |
public static final String SYNC_CIRCUIT_BREAKER_KEY
CircuitBreaker#successThreshold()
of
value greater than 1 is not supported.
Moreover, circuit breaker does not necessarily transition from CLOSED to OPEN immediately when a fault tolerance operation completes. See also Hystrix configuration
In general, application developers are encouraged to disable this feature on high-volume circuits and in production environments.
public HystrixCommandInterceptor(Boolean nonFallBackEnable, Config config, <any> fraction, BeanManager beanManager, RequestContext requestContext)
Copyright © 2018 JBoss by Red Hat. All rights reserved.