-
Notifications
You must be signed in to change notification settings - Fork 8.1k
New issue
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
Slot Chain 加载顺序问题导致网关限流规则不生效 order of the slot chain builder confusing #1306
Comments
查了下好像是这里没有始化网关的 |
Sentinel网关限流规则会转换为热点规则,看上去是依赖项少了。 如果使用SCA的 |
具体加载到了哪个 slot chain?贴一下所有引的 Spring Cloud Alibaba 和 Sentinel 相关的依赖。 |
已经定位问题,临时接了下,问题是SPI加多个载顺序问题,钉钉上面详细回复了 |
Hi 请教一下 集成spring cloud gateway之后,流控规则是如何持久化呢? |
流控规则持久化,我看了下,应该是和之前一样的,继续加DynamicRuleProvider DynamicRulePublisher,改GatewayApiController,GatewayFlowRuleController |
在2个controller中都没有发现DynamicRuleProvider 、DynamicRulePublisher 相关的引用呢 |
浏览了一下,是需要自己改造一个类似FlowControllerV2 的GatewayFlowRuleControllerV2类是吧?请问下,您那边之前有改造过吗,方便提供一份吗? |
我在自己的项目META-INF/services里面加了一个自己的SlotChainBuilder(复制于GatewaySlotChainBuilder),期待ServiceLoader的迭代顺序能早于HotParamSlotChainBuilder,结果果然成功了,网关流控也生效了。不过我的办法还是很怪异,希望有最新的版本修正这个问题。 |
Issue Description
Type: bug report or feature request
Describe what happened (or what feature you want)
spring cloud 2.2.0 对接 sentinel 1.7.1,限流功能无效
Describe what you expected to happen
spring cloud 2.2.0 对接 sentinel 1.7.1,能正常限制请求流量
How to reproduce it (as minimally and precisely as possible)
Tell us your environment
Anything else we need to know?
The text was updated successfully, but these errors were encountered: