-
Notifications
You must be signed in to change notification settings - Fork 12.6k
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
【将服务从nacos上下线后一直还能接收到请求】Requests continue to be received after the service is offline from nacos #12077
Comments
|
你好,网关没有地址缓存; 我通过设置如下参数解决了该问题
有个疑问 ,将上面的参数时间设置变小,会不会影响到naocs,生产用这些参数会产生什么影响??谢谢 |
|
preserved.heart.beat.interval 这失效了吗 我已经在生产环境改了以上三个参数 请教大佬 |
@dxiyang 人家回复的时候说过了, 2.x的客户端已经无效了, 因为原理上就不同了。 1.x的客户端是通过心跳来续约, 所以需要调整心跳间隔,过期时间, 2.x客户端是长连接保持。不需要心跳 |
是否有压力需要根据你服务端的规格,客户端的版本来评估, 如果是1.x的客户端, 默认值是5000, 15000,30000, 不建议改动的太低,太低的话即使没有压力,也会因为网络波动造成大量抖动。 如果是2.x客户端,那就不用调整了。 |
我是2.x的客户端,
上述下线服务异常,我在本地无法复现,但是我们生产环境确实存在,只能通过修改参数让其生效(下线后过大概30秒后不会有流量进入) |
【微服务架构,上层网关,下面有个服务A,服务A启动了两个实例,nacos是集群部署的】The microservice architecture, the upper gateway, has A service A underneath it, and Service A starts two instances, nacos is deployed in clusters
1、【用jemter一直模拟请求,然后将服务A的某个示例下线,按理来说过30秒左右该实例不会收到请求】
Using jemter to simulate requests all the time, and then taking an example of service A offline, the instance should not receive requests after 30 seconds or so
2、【但是经过几轮jmeter测试,只有一两次下线后是正常的,其余的轮次在下线后还会有请求】
However, after several rounds of jmeter tests, only one or two offline are normal, and the rest of the rounds will still have requests after offline
备注:nacos和服务不在一个局域网内
The text was updated successfully, but these errors were encountered: