blocks|key|4390060|text|作为将来的参考:我最终通过ConfigurationManager和一个字符串属性使用了这些设置。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4390061|ConfigurationManager.getConfigInstance().setProperty("...")|code-block|syntax|javascript|4390062|它让我改变了一些东西，但是比起原来的代码，它的类型安全性更低。我确实为字符串中的一个打字错误挣扎了一段时间，这就是为什么我想要避免这种情况。|4390063|我现在将它用于更改运行时所需的所有属性。每次有变化时创建一个新的Hystrix断路器(新的命令键)也是一个选项，但稍后会使用属性文件中断。|4390064|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

For future reference: I ended up using the settings through ConfigurationManager and a string property.

<pre><code>ConfigurationManager.getConfigInstance().setProperty("...")
</code></pre>

It let's me change things, but in a less type-safe way than the original code. I did struggle for some time with a typo in the string which is why I'd like to avoid that.

I now use this for all the properties I need to change runtime. Creating a new Hystrix circuit breaker every time something changes (new command key) could be an option as well, but would break using properties files later on.

blocks|key|4390385|text|回答晚了，但今天我也遇到了同样的问题，并找到了一种方法。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4390386|默认属性管理器的实现方式是，它根据您运行的命令名使用HystrixCommandProperties缓存。在第一次使用该命令时，它会缓存从传递给该命令的构造函数的HystrixCommandProperties.Setter中获得的内容，仅此而已。|offset|length|style|CODE|4390387|但是，使用自定义HystrixPropertiesStrategy作为Plugin，您可以覆盖缓存键(因此强制Hystrix重新计算传递给新命令实例的Setter，因为缓存键是新的，所以它认为它是新的命令)。|4390388|然后，代码将类似于以下内容：|4390389|public+HystrixCommandFactory(....)+{
++++HystrixPlugins.getInstance().registerPropertiesStrategy(new+HystrixPropertiesStrategyWithReloadableCache());
++++updateHystrixSettings();++++++++
}

//configurable+attributes
private+volatile+int+commandTimeoutMillis;
private+volatile+long+lastSettingsUpdatedTimestamp;
private+volatile+HystrixCommand.Setter+setterForNewCommands;

private+void+updateHystrixSettings()+{
++++lastSettingsUpdatedTimestamp+=+LocalDateTime.now().toDateTime().getMillis();
++++HystrixCommandProperties.Setter+propertiesSetter+=+HystrixCommandProperties.Setter()
++++++++.withExecutionTimeoutInMilliseconds(commandTimeoutMillis)
++++++++.withExecutionTimeoutEnabled(true);

++++this.setterForNewCommands+=+HystrixCommand.Setter
++++++++.withGroupKey(HystrixCommandGroupKey.Factory.asKey(GROUP_NAME))
++++++++.andCommandPropertiesDefaults(propertiesSetter);

}

public+void+setCommandTimeoutMillis(int+commandTimeoutMillis)+{+++++
++++this.commandTimeoutMillis+=+commandTimeoutMillis;
++++updateHystrixSettings();++++++++
}

private+class+HystrixPropertiesStrategyWithReloadableCache+extends+HystrixPropertiesStrategy+{

++++@Override
++++public+String+getCommandPropertiesCacheKey(HystrixCommandKey+commandKey,+HystrixCommandProperties.Setter+builder)+{
++++++++return+String.format("%25s-%25d",+commandKey.name(),+lastSettingsUpdatedTimestamp);
++++}
}|code-block|syntax|javascript|4390390|或者，您也可以始终从getCommandPropertiesCacheKey方法返回null+(这将完全关闭缓存)，但是这样就会产生Hystrix必须在每次调用命令时重新构建HystrixCommandProperties的开销|4390391|PS:确保使用适当的线程同步来读取和更新这些属性，因为这些属性将从不同的线程调用。为简单起见，我在此示例中省略了这一点，但实际上我在代码中使用了ReentrantReadWriteLock来保护对这些变量的访问|4390392|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/Netflix/Hystrix/wiki/Plugins^0|0|Q|O|29|V|0|8|P|Z|6|0|0|0|0|A|S|16|4|2F|O|0|20|M|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|13|8|@$D|14|E|15|F|G]|$D|16|E|17|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|18|8|@$D|19|E|1A|F|G]]|9|@$D|1B|E|1C|1|1D]]|A|$]]|$1|J|3|K|5|6|7|1E|8|@]|9|@]|A|$]]|$1|L|3|M|5|N|7|1F|8|@]|9|@]|A|$O|P]]|$1|Q|3|R|5|6|7|1G|8|@$D|1H|E|1I|F|G]|$D|1J|E|1K|F|G]|$D|1L|E|1M|F|G]]|9|@]|A|$]]|$1|S|3|T|5|6|7|1N|8|@$D|1O|E|1P|F|G]]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]]|V|$W|$5|X|Y|Z|A|$10|11]]]]

Late answer, but today i struggled with the same thing and found a way.

The way the default property manager is implemented is that it uses a cache of <code>HystrixCommandProperties</code> based on the name of the command you run. On the first use of the command, it caches what it gets out of the <code>HystrixCommandProperties.Setter</code> passed to the Command's constructor and that's it.

However, using the custom <code>HystrixPropertiesStrategy</code> as a <a href="https://github.com/Netflix/Hystrix/wiki/Plugins" rel="noreferrer">Plugin</a> you can override the cache key (and hence force Hystrix to re-evaluate the Setter passed to the new Command instance, because the cache key is new, so it thinks it's a new Command). 

The code would then look similar to this:

<pre><code>public HystrixCommandFactory(....) {
 HystrixPlugins.getInstance().registerPropertiesStrategy(new HystrixPropertiesStrategyWithReloadableCache());
 updateHystrixSettings(); 
}

//configurable attributes
private volatile int commandTimeoutMillis;
private volatile long lastSettingsUpdatedTimestamp;
private volatile HystrixCommand.Setter setterForNewCommands;

private void updateHystrixSettings() {
 lastSettingsUpdatedTimestamp = LocalDateTime.now().toDateTime().getMillis();
 HystrixCommandProperties.Setter propertiesSetter = HystrixCommandProperties.Setter()
 .withExecutionTimeoutInMilliseconds(commandTimeoutMillis)
 .withExecutionTimeoutEnabled(true);

 this.setterForNewCommands = HystrixCommand.Setter
 .withGroupKey(HystrixCommandGroupKey.Factory.asKey(GROUP_NAME))
 .andCommandPropertiesDefaults(propertiesSetter);

}

public void setCommandTimeoutMillis(int commandTimeoutMillis) { 
 this.commandTimeoutMillis = commandTimeoutMillis;
 updateHystrixSettings(); 
}

private class HystrixPropertiesStrategyWithReloadableCache extends HystrixPropertiesStrategy {

 @Override
 public String getCommandPropertiesCacheKey(HystrixCommandKey commandKey, HystrixCommandProperties.Setter builder) {
 return String.format("%s-%d", commandKey.name(), lastSettingsUpdatedTimestamp);
 }
}
</code></pre>

Alternatively, you could always return <code>null</code> from the <code>getCommandPropertiesCacheKey</code> method (that completely turns off caching), but then you have the overhead of Hystrix having to reconstruct the <code>HystrixCommandProperties</code> each time a Command is called

PS: Be sure to use proper thread synchronization for reading and updating these properties, because those will be called from different threads. I omitted that in this sample for simplicity, but I actually use a <code>ReentrantReadWriteLock</code> in my code to guard accesses to these variables

blocks|key|4390438|text|有一种非常简单的方法可以做到这一点。它只需要两个步骤:+a.注册正确的插件b.使用所需的覆盖添加正确的策略。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4390439|使用案例:将ExecutionTimeoutInMilliseconds从1000ms覆盖到30000+ms|4390440|HystrixPlugins.getInstance().registerPropertiesStrategy(new+HystrixPropertiesStrategy()+{
++++++++++++@Override
++++++++++++public+HystrixCommandProperties+getCommandProperties(HystrixCommandKey+commandKey,+HystrixCommandProperties.Setter+builder)+{
++++++++++++++++HystrixCommandProperties.Setter+timeout
++++++++++++++++++++++++=+HystrixCommandProperties.Setter().withExecutionTimeoutInMilliseconds(30000);
++++++++++++++++return+super.getCommandProperties(commandKey,+timeout);
++++++++++++}
++++++++});|code-block|syntax|javascript|4390441|在这里，我只是覆盖了所需的属性。当你运行你的应用程序时，你可以在调试模式下看到：|4390442|2018-06-08+23:18:32+[main]+DEBUG+c.n.h.s.p.HystrixPropertiesChainedProperty+-+Flipping+property:+hystrix.command.Client#getAllData().execution.isolation.thread.timeoutInMilliseconds+to+use+its+current+value:+30000|4390443|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

There is a very simple way of doing this. It just needs 2 steps:
a. registering the right plugin
b. Adding the correct strategy with the required override.

Use-case: Override ExecutionTimeoutInMilliseconds to 30000 ms from 1000 ms

<pre><code>HystrixPlugins.getInstance().registerPropertiesStrategy(new HystrixPropertiesStrategy() {
 @Override
 public HystrixCommandProperties getCommandProperties(HystrixCommandKey commandKey, HystrixCommandProperties.Setter builder) {
 HystrixCommandProperties.Setter timeout
 = HystrixCommandProperties.Setter().withExecutionTimeoutInMilliseconds(30000);
 return super.getCommandProperties(commandKey, timeout);
 }
 });
</code></pre>

Here I am just overriding the required property. When you run your application you can see this in the DEBUG mode:

<pre><code>2018-06-08 23:18:32 [main] DEBUG c.n.h.s.p.HystrixPropertiesChainedProperty - Flipping property: hystrix.command.Client#getAllData().execution.isolation.thread.timeoutInMilliseconds to use its current value: 30000
</code></pre>

I have a circuit breaker set up that I would like to change parameters for runtime. Things like threads and timeout needs to be tuned at customer site.

I create a HystrixCommandProperties.Setter like this:

<pre><code>HystrixCommandProperties.Setter hystrixProps = 
 HystrixCommandProperties.defaultSetter()
 .withCircuitBreakerSleepWindowInMilliseconds(myconf.sleepWindow);
HystrixThreadPoolProperties.Setter threadPoolSettings = 
 HystrixThreadPoolProperties.Setter()
 .withCoreSize(myconf.threadPoolSize);

new MyCommand(HystrixCommand.Setter.withGroupKey("mygroup")
 .andCommandPropertiesDefaults(hystrixProps)
 .andThreadPoolPropertiesDefaults(threadPoolSettings));
</code></pre>

MyCommand implements standard HystrixCommand and calls super(hystrixProps).

This works the first time, but when I try to change the properties at runtime (same group name) nothing happens. Is there another way to programmatically change this? 

I don't want to go through the property files or specifying an URL to Archaius. 

There are also answers that tells me to go through Archaius with ConfigurationManager.getConfigInstance().setProperty("...") . But surely there has to be a way that is similar to the original setters I create? Doing it completely different because it's the second time around just feels awkward.

Programmatically changing Hystrix properties

我有一个断路器设置，我想要更改运行时的参数。像线程和超时这样的东西需要在客户现场进行调整。我创建一个HystrixCommandProperties.Setter，如下所示：HystrixCommandProperties.Setter hystrixProps =     HystrixCommandProperti...

问以编程方式更改Hystrix属性
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问以编程方式更改Hystrix属性EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问以编程方式更改Hystrix属性
EN