blocks|key|1998346|text|对于这一点没有单一的设置。您需要设置多个参数来禁用Hystrix。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1998347|有关配置选项，请参阅https://github.com/Netflix/Hystrix/wiki/Configuration：|offset|length|1998348|hystrix.command.default.execution.isolation.strategy=SEMAPHORE
hystrix.command.default.execution.isolation.semaphore.maxConcurrentRequests=100000+#+basically+'unlimited'
hystrix.command.default.execution.timeout.enabled=false+
hystrix.command.default.circuitBreaker.enabled=false
hystrix.command.default.fallback.enabled=false|code-block|syntax|javascript|1998349|请仔细检查您的Hystrix版本以获取可用的参数。|1998350|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/Netflix/Hystrix/wiki/Configuration^0|0|A|1H|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@$D|W|E|X|1|Y]]|A|$]]|$1|F|3|G|5|H|7|Z|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|10|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]]]

There is no single setting for this. You'll need to set multiple parameters to disable Hystrix.

See <a href="https://github.com/Netflix/Hystrix/wiki/Configuration" rel="noreferrer">https://github.com/Netflix/Hystrix/wiki/Configuration</a> for the configuration options:

<pre><code>hystrix.command.default.execution.isolation.strategy=SEMAPHORE
hystrix.command.default.execution.isolation.semaphore.maxConcurrentRequests=100000 # basically 'unlimited'
hystrix.command.default.execution.timeout.enabled=false 
hystrix.command.default.circuitBreaker.enabled=false
hystrix.command.default.fallback.enabled=false
</code></pre>

Please double check your version of Hystrix for the available parameters.

blocks|key|86737|text|这就是你所需要的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|86738|#+Disable+Circuit+Breaker+(Hystrix)

spring:
++cloud:
++++circuit:
++++++breaker:
++++++++enabled:+false

hystrix:
++command:
++++default:
++++++circuitBreaker:
++++++++enabled:+false|code-block|syntax|javascript|86739|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

This is all what you need:

<pre><code># Disable Circuit Breaker (Hystrix)

spring:
 cloud:
 circuit:
 breaker:
 enabled: false

hystrix:
 command:
 default:
 circuitBreaker:
 enabled: false
</code></pre>

blocks|key|4865169|text|正如ahus1所说，没有单一的方法可以完全禁用Hystrix。为了在我们的应用程序中禁用它，我们认为将HystrixCommand放在包装类中是最干净、最安全的，而且包装类只公开了我们使用的HystrixCommand的一部分(在本例中是execute()方法)。在构造包装器类时，我们向它传递一个Callable，其中包含我们想要执行的代码，如果Hystrix被禁用(根据我们自己的配置值)，我们只需调用该Callable，而无需创建HystrixCommand。这避免了执行任何Hystrix代码，并且更容易说Hystrix在被禁用时根本不会影响我们的应用程序。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4865170|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

As ahus1 said, there is no single way to disable Hystrix entirely. To disable it in our application, we decided it was cleanest and safest to put a HystrixCommand in a wrapper class, and that wrapper class only exposed the parts of the HystrixCommand that we used (in our case, the execute() method). When constructing the wrapper class, we pass it a Callable that contains the code we want executed, and if Hystrix is disabled (according to our own config value), we simply call that Callable without ever creating a HystrixCommand. This avoids executing any Hystrix code whatsoever and makes it easier to say that Hystrix isn't affecting our application at all when it's disabled.

blocks|key|4865296|text|有几种方法可以实现这一点-|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4865297|4865298|为您的每个组执行此操作，包括default。虽然这不会禁用hystrix+(它只会一直保持电路闭合)，但您将获得相同的结果-+hystrix.command.{group-key}.circuitBreaker.forceClosed=false|ordered-list-item|offset|length|style|CODE|4865299|If您正在使用java，您可以在@HystrixCommand注释上创建一个环绕建议，并根据一个标志绕过hystrix的执行。|4865300|4865301|Java代码#2-|4865302|@Pointcut("@annotation(com.netflix.hystrix.contrib.javanica.annotation.HystrixCommand)")
public+void+hystrixCommandAnnotationPointcut()+{
}

@Around("hystrixCommandAnnotationPointcut()")
public+Object+methodsAnnotatedWithHystrixCommand(final+ProceedingJoinPoint+joinPoint)+throws+Throwable+{
Object+result+=+null;
Method+method+=+AopUtils.getMethodFromTarget(joinPoint);
if+((System.getProperty(enable.hystrix).equals("true"))+{
++++result+=+joinPoint.proceed();
}+else+{
++++result+=+method.invoke(joinPoint.getTarget(),+joinPoint.getArgs());
}
++++return+result;
}|code-block|syntax|javascript|4865303|entityMap^0|0|0|1R|1O|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|W|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|X|8|@$F|Y|G|Z|H|I]]|9|@]|A|$]]|$1|J|3|K|5|E|7|10|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|11|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|12|8|@]|9|@]|A|$]]|$1|O|3|P|5|Q|7|13|8|@]|9|@]|A|$R|S]]|$1|T|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|U|$]]

There are a couple of ways to achieve this-

<ol>
<li>Doing this for your every group including default. Although this will not disable hystrix(it will only keep the circuit closed all the time) but you will achieve the same result-
<code>hystrix.command.{group-key}.circuitBreaker.forceClosed=false</code></li>
<li>If you are using java, you can create an around advice over @HystrixCommand annotation and bypass hystrix execution based upon a flag. </li>
</ol>

Java Code for #2-

<pre><code>@Pointcut("@annotation(com.netflix.hystrix.contrib.javanica.annotation.HystrixCommand)")
public void hystrixCommandAnnotationPointcut() {
}

@Around("hystrixCommandAnnotationPointcut()")
public Object methodsAnnotatedWithHystrixCommand(final ProceedingJoinPoint joinPoint) throws Throwable {
Object result = null;
Method method = AopUtils.getMethodFromTarget(joinPoint);
if ((System.getProperty(enable.hystrix).equals("true")) {
 result = joinPoint.proceed();
} else {
 result = method.invoke(joinPoint.getTarget(), joinPoint.getArgs());
}
 return result;
}
</code></pre>

blocks|key|4865217|text|如果您的项目是spring托管的，则可以在applicationContext.xml中注释hystrixAspect的bean定义，注释以下行|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4865218|4865219|+bean+id="hystrixAspect"class="com.netflix.hystrix.contrib.javanica.aop.aspectj.HystrixCommandAspect"/>|blockquote|4865220|4865221|4865222|这将从您的项目中删除Hystrix。|4865223|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|M|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|N|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|O|8|@]|9|@]|A|$]]|$1|G|3|-4|5|6|7|P|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|Q|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|K|$]]

If your Project is spring Managed you can comment the bean definition of hystrixAspect in applicationContext.xml
Comment the following line

<blockquote>
 bean id="hystrixAspect"class="com.netflix.hystrix.contrib.javanica.aop.aspectj.HystrixCommandAspect"/>
</blockquote>

This will remove Hystrix from your project.

blocks|key|4865329|text|我遇到了这种情况，我想使用单个属性完全关闭Hystrix+(我们使用IBM+uDeploy来管理动态属性)。我们正在使用基于Hystrix构建的javanica库。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4865330|创建用于创建HystrixCommandAspect的配置类|4865331|ordered-list-item|4865332|4865333|​|4865334|@Configuration
++++++++public+class+HystrixConfiguration{

@Bean(name+=+"hystrixCommandAspect")
@Conditional(HystrixEnableCondition.class)
public+HystrixCommandAspect+hystrixCommandAspect(){+
++++++return+new+HystrixCommandAspect()}
}



2.+And+the+conditional+class+would+be+enabled+based+on+a+system+property.



+public+class+HystrixEnableCondition+implements+Condition{

++@Override
++public+boolean+matches(ConditionContext+context,+AnnotatedTypeMetadata+metadata){
++++return+
+++++++"YES".equalsIgnoreCase(
+++++++++++context.getEnvironment().getProperty("circuitBreaker.enabled"))+%7C%7C

+++++++"YES".equalsIgnoreCase(
+++++++++++System.getProperty("circuitBreaker.enabled"));
++}

+}|code-block|syntax|javascript|4865335|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|-4|5|E|7|R|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|T|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|U|8|@]|9|@]|A|$L|M]]|$1|N|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|O|$]]

I ran into this situation where I wanted to completely turnoff Hystrix using a single property (We use IBM uDeploy to manage dynamic properties). We are using javanica library built on top of Hystrix

<ol>
<li>Create a Configuration class which creates the HystrixCommandAspect</li>
</ol>

<pre><code>

@Configuration
 public class HystrixConfiguration{

<pre><code>@Bean(name = "hystrixCommandAspect")
@Conditional(HystrixEnableCondition.class)
public HystrixCommandAspect hystrixCommandAspect(){ 
 return new HystrixCommandAspect()}
}
</code></pre>

</pre></code>
2. And the conditional class would be enabled based on a system property.

<pre><code>

 public class HystrixEnableCondition implements Condition{

 @Override
 public boolean matches(ConditionContext context, AnnotatedTypeMetadata metadata){
 return 
 "YES".equalsIgnoreCase(
 context.getEnvironment().getProperty("circuitBreaker.enabled")) ||

 "YES".equalsIgnoreCase(
 System.getProperty("circuitBreaker.enabled"));
 }

 }
</code></pre>

blocks|key|86786|text|设置hystrix.command.default.execution.isolation.strategy=SEMAPHORE就足够了。此外，您还可以或应该使用hystrix.command.default.execution.timeout.enabled=false禁用超时线程|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|86787|entityMap^0|2|1Q|29|1J|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

setting
<code>hystrix.command.default.execution.isolation.strategy=SEMAPHORE</code>
is enough.
Additionally you may or should disable also the timeout threads
with <code>hystrix.command.default.execution.timeout.enabled=false</code>

I am integrating Hystrix in an application. That application is already in production and we will be testing out hystrix integration work in sandbox before we will push it to production. 
My question is that is there any way to turn on/off hystrix functionality using some configuration setting?

Turn off Hystrix functionality

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我正在将Hystrix集成到应用程序中。该应用程序已经投入生产，在将其推向生产之前，我们将在沙箱中测试hystrix集成工作。我的问题是，有没有办法使用一些配置设置来打开/关闭hystrix功能？

问关闭Hystrix功能
EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问关闭Hystrix功能EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问关闭Hystrix功能
EN