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
参考了 #9679 #9673
调用链路:
consumer双发现,注册2个nacos地址
dubbo: registries: nacosA: address: nacosA zone: nacosA group: nacosA cluster: failsafe
nacosB: address: nacosB zone: nacosB group: nacosB cluster: failsafe
现象: 启用cluster: failsafe时,会进行AbstractClusterInvoker.doSelect进行二选一,后续无法进入ZoneAwareClusterInvoker使用zone过滤
当不使用cluster: failsafe时,会进入ZoneAwareClusterInvoker,但是clusterInovker.isAvailable均为false
The text was updated successfully, but these errors were encountered:
Please try on 3.2.5. 2.7.x is no longer maintained.
Sorry, something went wrong.
经过排查,目前发现是多注册中心情况下 invoker-> cachedInvoker会被覆盖,导致实际该注册中心下的节点不属于自己,截止到2.7.22未修复
@Meedly Does it still exist in 3.2.x?
No news is good news. Please feel free to create a new issue if you have any question.
No branches or pull requests
参考了 #9679 #9673
调用链路:
consumer双发现,注册2个nacos地址
dubbo:
registries:
nacosA:
address: nacosA
zone: nacosA
group: nacosA
cluster: failsafe
现象:
启用cluster: failsafe时,会进行AbstractClusterInvoker.doSelect进行二选一,后续无法进入ZoneAwareClusterInvoker使用zone过滤
当不使用cluster: failsafe时,会进入ZoneAwareClusterInvoker,但是clusterInovker.isAvailable均为false
The text was updated successfully, but these errors were encountered: