Pre-check
- [x] I am sure that all the content I provide is in English.
Search before asking
- [x] I had searched in the issues and found no similar issues.
Apache Dubbo Component
Java SDK (apache/dubbo)
Dubbo Version
Dubbo Java 3.2.13, JDK 8, Mac OS/Linux
Steps to reproduce this issue
In one Dubbo project use Nacos as registry center, there are several interfaces, and set different registry.group for each interface, that will established one connection to Nacos for each interface(registry.group), so it causes too many connections to be established.
I check the code in class org.apache.dubbo.registry.nacos.NacosRegistryFactory, in the method createRegistry will create a NamingService every time.
Is it neccessary to create a new NamingService every time for each different registry.group ?
some related code:
What you expected to happen
Establish only one NamingService Connection for each Nacos Host，not for each registry.group
Anything else
No response
Are you willing to submit a pull request to fix on your own?
- [x] Yes I am willing to submit a pull request on my own!
Code of Conduct
- [x] I agree to follow this project's Code of Conduct
Comment From: zrlw
what's your dubbo.registry.register-mode? if you choose dubbo3 + nacos2.x, you'd better only use instance mode, or use zk as your registry center if you keep using interface mode.
Comment From: goto456
what's your dubbo.registry.register-mode? if you choose dubbo3 + nacos2.x, you'd better only use instance mode, or use zk as your registry center if you keep using interface mode.
I used instance mode, dubbo 3.2.13 + nacos 2.1.0
Comment From: zrlw
how many groups do you have? how much less will the connections number be if share connection between different registry groups?