-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
服务端启动新实例时,消费端调用不到,需要重启消费端 #1940
Comments
非常感谢,我们会尽量在正式release解决这个问题 |
排查了一天,确定这个不是SCA这边的问题,有可能出在网络连通上,或者是dubbo上。
|
另外,SCA 的版本,建议升级到 2.2.5.RC2 |
最后一个截图是Provider已经下线,Consumer还在尝试重连 port用的是-1,今天再用2.2.5.RC2测试一下
|
dubbo.protocol.port 不要用 -1 ,提前分配好 |
有什么联系方式,方便单独沟通一下吗? |
钉钉号:ztwrhde |
我这边出现了跟这一样的问题 版本 钉钉:megatronyy |
@twfx7758 你是用的是哪个版本? |
版本 |
升级到 2.2.5.RELEASE 应该就能解决你的问题了 |
多谢,已升级,我们再观察下 |
该issue先关闭了,如果还有问题,另提issue再继续; |
@theonefx dubbo配置如下,服务端和消费端一样
registry:
address: spring-cloud://nacos.test.xxx.cn:8080
consumer:
timeout: 10000
check: true
protocol:
name: dubbo
port: -1
两个机器,IP为121和122,分别部署两个Provider,在122上部署Consumer,访问http://122:8800/dubbo/get/1 来测试dubbo接口是否可用,以下方便描述我用Provider-122,Provider-121,Consumer-122来代表实例
第一步,先启动Provider-122和Consumer-122实例,访问/dubbo/get/1正常。
第二步,再启动Provider-121,Provider-122和Consumer-122都会收到InstancesChangeEvent,nacos也注册成功
访问/dubbo/get/1正常,dubbo请求只会打到第一次启动的122(如果先启动两个Provider,load balance是正常的)
第三步,停止Provider-122,用的kill命令,Provider-121和Consumer-122都会收到InstancesChangeEvent,nacos取消注册成功
访问/dubbo/get/1报错,提示Tried 3 times of the providers [172.24.30.122:20881] (1/1);
ReconnectTimerTask 一直在检测已经下线的Provider-122
Originally posted by @caichy in #1805 (comment)
The text was updated successfully, but these errors were encountered: