We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
场景: 实现单个节点熔断降级功能,比如:线上有4个节点,其中一个节点在某一时间出现网络异常,需要进行故障隔离。
方案: 通过applicationName+ip方式设置资源名称,然后触发熔断规则时,自动剔除此Ip节点,恢复后在正常调用。这样做的弊端就是如果节点数过多,无法批量设置!应该怎么优化?
The text was updated successfully, but these errors were encountered:
这种情况,是不是不使用sentinel好一些。简单粗暴的问题服务注册与发现通过心跳和健康检查可以做到。如果需要精细控制可以考虑扩展服务注册与发现的健康检查接口,查询监控工具api(skywalking等)获取平均响应时长、接口失败率等进行来判断是否需要暂时下线。
Sorry, something went wrong.
用apm去做肯定不行啊,首先这个中间件职责的划分就是sentinel负责,你看看商业版他是支持的,同时sentinel相关负责人说2.0会去实现这个功能。其次就是基于apm数据会有滞后性,稳定性也是一个问题
No branches or pull requests
场景:
实现单个节点熔断降级功能,比如:线上有4个节点,其中一个节点在某一时间出现网络异常,需要进行故障隔离。
方案:
通过applicationName+ip方式设置资源名称,然后触发熔断规则时,自动剔除此Ip节点,恢复后在正常调用。这样做的弊端就是如果节点数过多,无法批量设置!应该怎么优化?
The text was updated successfully, but these errors were encountered: